[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71ACE1GQQHAE4SV700AHCZ6":3,"skill-same:01M71ACE1GQQHAE4SV700AHCZ6":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M71ACE1GQQHAE4SV700AHCZ6","bencium-code-conventions",null,"Bence's code style, tech stack, and workflow conventions","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fdesign-skills\u002Fbencium-code-conventions\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"code conventions","code","conventions","bencium code conventions","setting","projects","tech","for","up","writing","when","workflow","stack","style","code style","2026-11-10 10:12:30",false,"---\nname: bencium-code-conventions\ndescription: Bence's code style, tech stack, and workflow conventions\nwhen_to_use: When writing code or setting up projects for Bence\n---\n\n# Code Conventions\n\n## Core Technologies\n- **Frontend:** ReactJS, Next.js (App Router structure), TypeScript\n- **Styling:** TailwindCSS v3.x (never v4), Shadcn UI\n- **Build Tools:** Vite (when applicable)\n- **Backend:** Postgres compatible convex.dev or Supabase (always ask, never local postgres)\n- **Deployment:** Netlify or Vercel or Fly - suggest\n- **Environment:** Mac M2, Python3 with virtual environments, no CUDA, no Docker\n- **Alternative Languages:** Avoid python if you can, try using RUST\n\n## Code Style & Structure\n- Use ES modules (import\u002Fexport) syntax\n- Destructure imports when possible\n- Use TypeScript for all new code\n- Use async\u002Fawait instead of Promise chains\n- Prefer const\u002Flet over var; use early returns\n- Use consts instead of functions: `const toggle = () =>`. Define types.\n- Use descriptive variable names with auxiliary verbs (e.g., `isLoading`, `hasError`)\n- Use lowercase with dashes for directory names (e.g., `components\u002Fauth-wizard`)\n\n## Framework Conventions\n- **Next.js:** Use App Router (app directory) structure and page.tsx files\n- **React:** Functional and declarative patterns; avoid classes\n- **State Management:** Zustand, TanStack React Query\n- **Validation:** Zod for schema validation\n\n## Component Library & Styling\n- **Component Library:** Prefer shadcn components from `@\u002Fcomponents\u002Fui`\n- **Styling:** Tailwind utility classes\n- **Layout:** Grid\u002Fflex wrappers with `gap` for spacing\n- **Icons:** `@phosphor-icons\u002Freact`\n- **Toasts:** `sonner` for notifications\n- Always add loading states, spinners, placeholder animations\n\n## Quality Assurance & Testing\n- **TDD:** Write failing tests first, commit them, then iterate until suite passes\n- Never mock tests - if there's a test script, execute all until done\n- Always write SQL in chunks with test steps after each chunk\n- Typecheck after making code changes\n- Run tests before committing\n- Prefer running single tests for performance, not whole suite\n\n## Error Handling\n- Implement proper error handling and user input validation\n- Error messages should be understood by non-technical people\n- Use early returns for error conditions\n- Test APIs via curl commands first, then implement in code\n\n## Performance & Architecture\n- Minimize `'use client'`, `useEffect`, `setState`; favor RSC and Next.js SSR\n- Implement dynamic imports for code splitting\n- Optimize images: WebP format, size data, lazy loading\n- Favor small, simple, well-named modules\n\n## Development Workflow\n**Process:** Explore → Plan → Code → Commit\n- Read relevant files\n- Think through a plan\n- Implement\n- Then commit\n- Never local backend, always ask (usually Supabase, Neon)\n- Minimal dependency, no docker\n\n## Environment & Deployment\n- Add .env files for API keys; warn me to save keys in Vercel\u002FNetlify env variables\n- Write code deployable to Netlify or Vercel; prepare to build locally first\n- Document progress in progress.md; ask for implementation plan\n","# Code Conventions\n\n## Core Technologies\n- **Frontend:** ReactJS, Next.js (App Router structure), TypeScript\n- **Styling:** TailwindCSS v3.x (never v4), Shadcn UI\n- **Build Tools:** Vite (when applicable)\n- **Backend:** Postgres compatible convex.dev or Supabase (always ask, never local postgres)\n- **Deployment:** Netlify or Vercel or Fly - suggest\n- **Environment:** Mac M2, Python3 with virtual environments, no CUDA, no Docker\n- **Alternative Languages:** Avoid python if you can, try using RUST\n\n## Code Style & Structure\n- Use ES modules (import\u002Fexport) syntax\n- Destructure imports when possible\n- Use TypeScript for all new code\n- Use async\u002Fawait instead of Promise chains\n- Prefer const\u002Flet over var; use early returns\n- Use consts instead of functions: `const toggle = () =>`. Define types.\n- Use descriptive variable names with auxiliary verbs (e.g., `isLoading`, `hasError`)\n- Use lowercase with dashes for directory names (e.g., `components\u002Fauth-wizard`)\n\n## Framework Conventions\n- **Next.js:** Use App Router (app directory) structure and page.tsx files\n- **React:** Functional and declarative patterns; avoid classes\n- **State Management:** Zustand, TanStack React Query\n- **Validation:** Zod for schema validation\n\n## Component Library & Styling\n- **Component Library:** Prefer shadcn components from `@\u002Fcomponents\u002Fui`\n- **Styling:** Tailwind utility classes\n- **Layout:** Grid\u002Fflex wrappers with `gap` for spacing\n- **Icons:** `@phosphor-icons\u002Freact`\n- **Toasts:** `sonner` for notifications\n- Always add loading states, spinners, placeholder animations\n\n## Quality Assurance & Testing\n- **TDD:** Write failing tests first, commit them, then iterate until suite passes\n- Never mock tests - if there's a test script, execute all until done\n- Always write SQL in chunks with test steps after each chunk\n- Typecheck after making code changes\n- Run tests before committing\n- Prefer running single tests for performance, not whole suite\n\n## Error Handling\n- Implement proper error handling and user input validation\n- Error messages should be understood by non-technical people\n- Use early returns for error conditions\n- Test APIs via curl commands first, then implement in code\n\n## Performance & Architecture\n- Minimize `'use client'`, `useEffect`, `setState`; favor RSC and Next.js SSR\n- Implement dynamic imports for code splitting\n- Optimize images: WebP format, size data, lazy loading\n- Favor small, simple, well-named modules\n\n## Development Workflow\n**Process:** Explore → Plan → Code → Commit\n- Read relevant files\n- Think through a plan\n- Implement\n- Then commit\n- Never local backend, always ask (usually Supabase, Neon)\n- Minimal dependency, no docker\n\n## Environment & Deployment\n- Add .env files for API keys; warn me to save keys in Vercel\u002FNetlify env variables\n- Write code deployable to Netlify or Vercel; prepare to build locally first\n- Document progress in progress.md; ask for implementation plan\n",{"name":5,"description":7,"when_to_use":44},"When writing code or setting up projects for Bence","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","design-skills\u002Fbencium-code-conventions",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-13 15:29:19",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add ariadoss\u002Fsuperskills --skill bencium-code-conventions",{"tool":61,"command":62},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill bencium-code-conventions",{"tool":64,"command":65},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill bencium-code-conventions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fdesign-skills\u002Fbencium-code-conventions\u002FSKILL.md",true,[],[70,98,121,140,169,185],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":39},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[72,82,83,84,85,86,87,88,89,34,90,91,92,93,94,95,96,97],"user","download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","use","subtitles","transcripts",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":39},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[105,106,85,107,108,109,110,25,111,34,112,113,114,115,116,31,117,118,119,120],"write plan","plan","dry","verification","review","tasks","you","auto","eng","coverage","complete","section","test plan","target","as","yagni",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":39},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[123,128,129,130,95,131,132,133,134,135,136,108,137,34,138,139],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":149,"publishedAt":39},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发",[150,151,152,153,154,155,156,157,158,34,159,160,161,162,163,164,165,166,167,168],"web","perf","web perf","resources","MCP","layout","optimize","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":39},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[171,115,176,177,136,108,178,179,34,180,95,181,182,183,184],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":39},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[192,193,194,195,196,197,198,34,199,95,200],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]