Docs
How the system works.
Pick batteries. We check that they work together, merge their files and write the agent layer for Claude Code, Codex and Cursor. 7 short pages explain how.
These pages are the whole story, in reading order. Already generated something? Skip to the first ten minutes. Every command is shown for bun, pnpm and npm.
PagesOverview
The pages
- 01How the generator worksThe path from a folder in registry/ to a repo on your disk: loader, resolver, mergers, compiler, generator, and the file in packages/core that owns each step.8 min read
- 02The agentic layerRules, skills, agents, hooks, solution docs and MCP servers. What each hook does, when it runs, and what Codex and Cursor get.8 min read
- 03Solo mode and team modeThe only difference is enforcement. Two hooks are off in solo and on in team. Here is exactly what each one refuses.4 min read
- 04The first ten minutesUnzip, install, fill in the env vars, sign in to your own app, run verify, prove the guard hooks still block, and write the first plan.4 min read
- 05Designs and the token contractWhat a design ships, why every design restyles the whole kit, how the previews are made, and how to use the designer agent.5 min read
- 06Contributing a batteryThe contract on one page: the folder shape, the gate every battery must pass, and the commands that are the whole review.5 min read
- 07FAQWhy there is no CI and no sync, why Next.js and Vercel only, what happens to your email address, and who owns the generated code.7 min read
Not what you were after
- The cookbook: every solution doc in the registry. Battery-specific problems live there, not here.
- Designs: the token sets and their reference screens, side by side.
- The builder: pick batteries and watch the file tree, the counts and the CLAUDE.md preview redraw as you go.