Scaffold
Invoke as $scaffold.
Use this skill when the user wants to create a new package or app in their monorepo.
For product/app workflows, $scaffold is normally downstream of research, prototype consolidation, production specification, roadmap, and phase planning. Use it when $roadmap/$plan-phase identifies that the next implementation step needs a new app/package root. Do not route from $idea-scope-brief, $bootstrap-repo, $icp, $competitive-analysis, $journey-map, $ux-variations, or $ui-interview directly to $scaffold unless the user explicitly asks to create a minimal shell first.
Process
- Parse the type (package/app) and name from arguments.
- Check
.agents/project.json. If it is missing, run or recommend $pack recommend and include the likely project type in the scaffold plan.
- If the scaffold creates a new project root, include
.agents/project.json and install the matching local pack with scripts/pack.sh install <pack> after the root exists.
- Learn conventions from CLAUDE.md, AGENTS.md,
.agents/project.json, and monorepo config.
- Find the most recently created package/app as a template.
- Present the scaffold plan and wait for approval. Use
update_plan to track the work; use request_user_input only if the session is already in Plan mode and a structured choice would help.
- Generate files, adapting the template with the new name.
- Run install and type-check to verify.
Output
- Scaffolded: type, name, location
- Files Created: list of generated files
- Next Steps: what to do after scaffolding
Next-Step Routing
- If the scaffold was created as part of an active roadmap/phase, recommend
$exec to continue the current implementation step.
- If the user explicitly requested an early shell before research, keep the next route on the research-first product workflow:
$icp when the concept is ready and business-discovery is enabled, otherwise $pack install business-discovery.
- If the scaffold is for a non-product package with no pending roadmap item, recommend
$roadmap or $plan-phase only when implementation sequencing is missing.
Constraints
- Always use an existing package as the reference template.
- Do not install domain packs globally; use project-local pack skill roots.
- Present the plan and get approval before creating files. Do not assume a Claude-style
EnterPlanMode or clear-context accept flow exists.
- Keep the scaffold minimal — no unnecessary boilerplate.
- Do not treat scaffolding as product validation. It creates structure only; ICP, market, journey, UX, UI, and prototype decisions belong to their upstream skills.
Default Shipping Contract
Follow the shared shipping contract convention in CLAUDE.md.
1---2name: scaffold-23description: Generate a new package or app in the monorepo following established project conventions4---5
6# Scaffold
7
8Invoke as `$scaffold`.
9
10Use this skill when the user wants to create a new package or app in their monorepo.
11
12For product/app workflows, `$scaffold` is normally downstream of research, prototype consolidation, production specification, roadmap, and phase planning. Use it when `$roadmap`/`$plan-phase` identifies that the next implementation step needs a new app/package root. Do not route from `$idea-scope-brief`, `$bootstrap-repo`, `$icp`, `$competitive-analysis`, `$journey-map`, `$ux-variations`, or `$ui-interview` directly to `$scaffold` unless the user explicitly asks to create a minimal shell first.
13
14## Process
15
161. Parse the type (package/app) and name from arguments.
172. Check `.agents/project.json`. If it is missing, run or recommend `$pack recommend` and include the likely project type in the scaffold plan.
183. If the scaffold creates a new project root, include `.agents/project.json` and install the matching local pack with `scripts/pack.sh install <pack>` after the root exists.
194. Learn conventions from CLAUDE.md, AGENTS.md, `.agents/project.json`, and monorepo config.
205. Find the most recently created package/app as a template.
216. Present the scaffold plan and wait for approval. Use `update_plan` to track the work; use `request_user_input` only if the session is already in Plan mode and a structured choice would help.
227. Generate files, adapting the template with the new name.
238. Run install and type-check to verify.
24
25## Output
26
27- **Scaffolded**: type, name, location
28- **Files Created**: list of generated files
29- **Next Steps**: what to do after scaffolding
30
31## Next-Step Routing
32
33- If the scaffold was created as part of an active roadmap/phase, recommend `$exec` to continue the current implementation step.
34- If the user explicitly requested an early shell before research, keep the next route on the research-first product workflow: `$icp` when the concept is ready and business-discovery is enabled, otherwise `$pack install business-discovery`.
35- If the scaffold is for a non-product package with no pending roadmap item, recommend `$roadmap` or `$plan-phase` only when implementation sequencing is missing.
36
37## Constraints
38
39- Always use an existing package as the reference template.
40- Do not install domain packs globally; use project-local pack skill roots.
41- Present the plan and get approval before creating files. Do not assume a Claude-style `EnterPlanMode` or clear-context accept flow exists.
42- Keep the scaffold minimal — no unnecessary boilerplate.
43- Do not treat scaffolding as product validation. It creates structure only; ICP, market, journey, UX, UI, and prototype decisions belong to their upstream skills.
44
45
46## Default Shipping Contract
47
48Follow the shared shipping contract convention in CLAUDE.md.
GeorgeQLe