Docs
How the system works.
Pick batteries. We check that they work together, merge their files and write the agent layer: an AGENTS.md any coding agent can read, plus files of their own for Claude Code, Codex, Cursor, GitHub Copilot and 6 more. 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.10 min read
- 02The agentic layerAGENTS.md, rules, skills, subagents, hooks, solution docs and MCP servers. What each hook does, which agents run it, and what each of the 10 agent targets gets.13 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, run /setup in your agent, sign in to your own app, run verify, prove the guard hooks still block, and write the first plan.5 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.6 min read
- 07FAQWhy there is no CI and no sync, why Next.js and Vercel only, which coding agents it works with, what happens to your email address, and who owns the generated code.8 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 AGENTS.md preview redraw as you go.