[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FWWHCGABEN85YJAPWVBTH3":3,"skill-same:01M6FWWHCGABEN85YJAPWVBTH3":63},{"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":18,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6FWWHCGABEN85YJAPWVBTH3","scaffold",null,"Generate a new package or app in the monorepo following established project conventions","GeorgeQLe\u002Fagentic-skills","GeorgeQLe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21134126?v=4","01M6D2JP418S0VGJGF8M93EC3H","George Le","01M6D2JPBAKYD82TA5FS6HKQ3D",1,"MIT","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fmonorepo\u002Fclaude\u002Fscaffold\u002Farchive\u002Fv0.1\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31],"dashboard","project conventions","generate","package","admin","execution","monorepo","v0","conventions","project","app","type","name","2026-11-10 10:12:30",false,"---\nname: scaffold\ndescription: Generate a new package or app in the monorepo following established project conventions\ntype: execution\nversion: v0.1\nargument-hint: \u003Ctype> \u003Cname> (e.g. \"package utils\" or \"app admin-dashboard\")\n---\n\n# Scaffold\n\nGenerate a new package or app in the monorepo that follows the project's established conventions and patterns.\n\nFor product\u002Fapp workflows, `\u002Fscaffold` is normally downstream of research, prototype consolidation, production specification, roadmap, and phase planning. Use it when `\u002Froadmap` or `\u002Fplan-phase` identifies that the next implementation step needs a new app\u002Fpackage root. Do not route from `\u002Fidea-scope-brief`, `\u002Fbootstrap-repo`, `\u002Fcustomer-discovery`, `\u002Fcompetitive-analysis`, `\u002Fjourney-map`, `\u002Fux-variations`, or `\u002Fui-interview` directly to `\u002Fscaffold` unless the user explicitly asks to create a minimal shell first.\n\n## Process\n\n1. **Parse the input** from `$ARGUMENTS`:\n   - Extract the type (`package` or `app`) and the name.\n   - If not provided or unclear, ask the user.\n\n2. **Learn the project's conventions:**\n   - Read `.agents\u002Fproject.json` when present. If it is missing, run or recommend `\u002Fpack recommend` and include the likely project type in the scaffold plan.\n   - If this scaffold creates a new project root, include `.agents\u002Fproject.json` and install the matching local pack with `scripts\u002Fpack.sh install \u003Cpack>` after the root exists.\n   - Read `CLAUDE.md` and `AGENTS.md` for project structure and conventions.\n   - Read the monorepo config (`turbo.json`, `pnpm-workspace.yaml`, or equivalent).\n   - Identify the directory pattern:\n     - Where do packages live? (`packages\u002F`, `libs\u002F`, etc.)\n     - Where do apps live? (`apps\u002F`, `services\u002F`, etc.)\n\n3. **Find a reference to copy from:**\n   - List existing packages\u002Fapps of the same type.\n   - Read the most recently created one (by git log) as the template.\n   - Identify the standard files:\n     - `package.json` (scripts, dependencies, exports)\n     - `tsconfig.json` (extends pattern)\n     - Source structure (`src\u002F`, `index.ts`, etc.)\n     - Test setup (if present)\n     - Any other config files (`.eslintrc`, `tailwind.config.*`, etc.)\n\n4. **Enter plan mode:**\n   - Enter plan mode using EnterPlanMode.\n   - Present the scaffold plan:\n     - Directory: where it will be created\n     - Files to generate (with brief content description)\n     - Dependencies to include\n     - Reference package used as template\n   - Wait for user approval.\n\n5. **Generate the scaffold after approval:**\n   - If Claude Code already returned to normal mode after approval, do not call ExitPlanMode again; continue directly with generation. Only use the plan-mode exit tool when the session is still visibly in plan mode.\n   - Create the directory structure.\n   - Generate each file, adapting the template:\n     - Update `name` in `package.json` to match the new package name.\n     - Update paths and references.\n     - Create minimal placeholder source files (`src\u002Findex.ts` with a basic export).\n     - Include the standard test setup if the project uses tests.\n   - Run `pnpm install` (or equivalent) to link the new package.\n   - Run type-checking to verify the scaffold compiles.\n\n## Output\n\n### Scaffolded\n- **Type**: package\u002Fapp\n- **Name**: `@scope\u002Fname`\n- **Location**: `packages\u002Fname\u002F`\n\n### Files Created\n- `packages\u002Fname\u002Fpackage.json`\n- `packages\u002Fname\u002Ftsconfig.json`\n- `packages\u002Fname\u002Fsrc\u002Findex.ts`\n- ...\n\n### Next Steps\n- What the user should do next (add dependencies, implement features, wire up routes, etc.)\n\n## Next-Step Routing\n\n- If the scaffold was created as part of an active roadmap\u002Fphase, recommend `\u002Fexec` to continue the current implementation step.\n- If the user explicitly requested an early shell before research, keep the next route on the research-first product workflow: `\u002Fcustomer-discovery` when the concept is ready and business-discovery is enabled, otherwise `\u002Fpack install business-discovery`.\n- If the scaffold is for a non-product package with no pending roadmap item, recommend `\u002Froadmap` or `\u002Fplan-phase` only when implementation sequencing is missing.\n\n## Constraints\n- Always use an existing package\u002Fapp as the reference template — do not invent conventions.\n- Do not install domain packs globally; use project-local pack skill roots.\n- Always enter plan mode before creating files.\n- Do not call ExitPlanMode from normal mode. If Claude Code reports \"You are not in plan mode\" after approval, treat approval as complete and continue implementation.\n- Do not add unnecessary boilerplate — keep the scaffold minimal and consistent with existing packages.\n- If the project does not appear to be a monorepo, inform the user and ask how to proceed.\n- Do not install external dependencies beyond what the template uses.\n- Do not treat scaffolding as product validation. It creates structure only; ICP, market, journey, UX, UI, and prototype decisions belong to their upstream skills.\n\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","# Scaffold\n\nGenerate a new package or app in the monorepo that follows the project's established conventions and patterns.\n\nFor product\u002Fapp workflows, `\u002Fscaffold` is normally downstream of research, prototype consolidation, production specification, roadmap, and phase planning. Use it when `\u002Froadmap` or `\u002Fplan-phase` identifies that the next implementation step needs a new app\u002Fpackage root. Do not route from `\u002Fidea-scope-brief`, `\u002Fbootstrap-repo`, `\u002Fcustomer-discovery`, `\u002Fcompetitive-analysis`, `\u002Fjourney-map`, `\u002Fux-variations`, or `\u002Fui-interview` directly to `\u002Fscaffold` unless the user explicitly asks to create a minimal shell first.\n\n## Process\n\n1. **Parse the input** from `$ARGUMENTS`:\n   - Extract the type (`package` or `app`) and the name.\n   - If not provided or unclear, ask the user.\n\n2. **Learn the project's conventions:**\n   - Read `.agents\u002Fproject.json` when present. If it is missing, run or recommend `\u002Fpack recommend` and include the likely project type in the scaffold plan.\n   - If this scaffold creates a new project root, include `.agents\u002Fproject.json` and install the matching local pack with `scripts\u002Fpack.sh install \u003Cpack>` after the root exists.\n   - Read `CLAUDE.md` and `AGENTS.md` for project structure and conventions.\n   - Read the monorepo config (`turbo.json`, `pnpm-workspace.yaml`, or equivalent).\n   - Identify the directory pattern:\n     - Where do packages live? (`packages\u002F`, `libs\u002F`, etc.)\n     - Where do apps live? (`apps\u002F`, `services\u002F`, etc.)\n\n3. **Find a reference to copy from:**\n   - List existing packages\u002Fapps of the same type.\n   - Read the most recently created one (by git log) as the template.\n   - Identify the standard files:\n     - `package.json` (scripts, dependencies, exports)\n     - `tsconfig.json` (extends pattern)\n     - Source structure (`src\u002F`, `index.ts`, etc.)\n     - Test setup (if present)\n     - Any other config files (`.eslintrc`, `tailwind.config.*`, etc.)\n\n4. **Enter plan mode:**\n   - Enter plan mode using EnterPlanMode.\n   - Present the scaffold plan:\n     - Directory: where it will be created\n     - Files to generate (with brief content description)\n     - Dependencies to include\n     - Reference package used as template\n   - Wait for user approval.\n\n5. **Generate the scaffold after approval:**\n   - If Claude Code already returned to normal mode after approval, do not call ExitPlanMode again; continue directly with generation. Only use the plan-mode exit tool when the session is still visibly in plan mode.\n   - Create the directory structure.\n   - Generate each file, adapting the template:\n     - Update `name` in `package.json` to match the new package name.\n     - Update paths and references.\n     - Create minimal placeholder source files (`src\u002Findex.ts` with a basic export).\n     - Include the standard test setup if the project uses tests.\n   - Run `pnpm install` (or equivalent) to link the new package.\n   - Run type-checking to verify the scaffold compiles.\n\n## Output\n\n### Scaffolded\n- **Type**: package\u002Fapp\n- **Name**: `@scope\u002Fname`\n- **Location**: `packages\u002Fname\u002F`\n\n### Files Created\n- `packages\u002Fname\u002Fpackage.json`\n- `packages\u002Fname\u002Ftsconfig.json`\n- `packages\u002Fname\u002Fsrc\u002Findex.ts`\n- ...\n\n### Next Steps\n- What the user should do next (add dependencies, implement features, wire up routes, etc.)\n\n## Next-Step Routing\n\n- If the scaffold was created as part of an active roadmap\u002Fphase, recommend `\u002Fexec` to continue the current implementation step.\n- If the user explicitly requested an early shell before research, keep the next route on the research-first product workflow: `\u002Fcustomer-discovery` when the concept is ready and business-discovery is enabled, otherwise `\u002Fpack install business-discovery`.\n- If the scaffold is for a non-product package with no pending roadmap item, recommend `\u002Froadmap` or `\u002Fplan-phase` only when implementation sequencing is missing.\n\n## Constraints\n- Always use an existing package\u002Fapp as the reference template — do not invent conventions.\n- Do not install domain packs globally; use project-local pack skill roots.\n- Always enter plan mode before creating files.\n- Do not call ExitPlanMode from normal mode. If Claude Code reports \"You are not in plan mode\" after approval, treat approval as complete and continue implementation.\n- Do not add unnecessary boilerplate — keep the scaffold minimal and consistent with existing packages.\n- If the project does not appear to be a monorepo, inform the user and ask how to proceed.\n- Do not install external dependencies beyond what the template uses.\n- Do not treat scaffolding as product validation. It creates structure only; ICP, market, journey, UX, UI, and prototype decisions belong to their upstream skills.\n\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":24,"version":37,"description":7,"argument-hint":38},"v0.1","\u003Ctype> \u003Cname> (e.g. \"package utils\" or \"app admin-dashboard\")","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fmonorepo\u002Fclaude\u002Fscaffold\u002Farchive\u002Fv0.1",0,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills","https:\u002F\u002Fagentic-skills-blush.vercel.app","https:\u002F\u002Fgithub.com\u002FGeorgeQLe","georgeqle.com","George Le is a futurist and serial tech entrepreneur who wants to work toward a world where humanity is free from robotic tasks.","2026-11-10 04:07:24",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill scaffold",{"tool":55,"command":56},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill scaffold",{"tool":58,"command":59},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill scaffold","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fmonorepo\u002Fclaude\u002Fscaffold\u002Farchive\u002Fv0.1\u002FSKILL.md",true,[],[64,76,86,98,113,124],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":32},"01M6G0NJES15RJKZE6YZ0TSYGF","source-checkout-allowed","Valid source-checkout-only fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fsource-checkout-allowed\u002FSKILL.md",[],[71,72,73,74,26,75],"source checkout allowed","checkout","fixture","only","valid",{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":32},"01M6G0NFZ3R1MNB1E3DVTM0WB7","deck-install-valid","Valid deck install fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fdeck-install\u002FSKILL.md",[],[83,84,85,75,73,26],"deck install valid","deck","install",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":32},"01M6G0ND3QZQC4MDZ9NVB97PT2","codex-pack-guard-valid","Valid Codex Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-pack-guard\u002FSKILL.md",[],[93,94,95,75,96,97,73,26],"codex pack guard valid","pack","guard","codex","availability",{"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":109,"publishedAt":32},"01M6G0NA9YB3NKGZKD3S96JMNB","codex-missing-skill-valid","Valid Codex missing skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-missing-skill-fallback\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[110,111,75,96,26,112,73],"codex missing skill valid","missing","fallback",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":32},"01M6G0N7PC0EKFD40ZWQAXSAQ9","codex-base-skill-fallback-valid","Valid Codex base skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-base-skill-fallback\u002FSKILL.md",[119],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[75,96,112,121,122,123,26,73],"base skill","codex base skill fallback valid","base",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":32},"01M6G0N4VRR2YKZQ6N3Y6S2BQA","claude-pack-guard-valid","Valid Claude Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fclaude-pack-guard\u002FSKILL.md",[],[75,95,94,131,97,26,73],"claude pack guard valid"]