Project Templates

init asks for your project type in the 3-question wizard and tailors the first project under projects/[name]/ to match. The zones and routing are the same for everyone; the template sets how much structure your first project starts with.

Nine types ship a full stage pipeline: one subfolder per stage, each with its own CONTEXT.md carrying a defined role, what "done" looks like for that stage, and the condition for moving to the next. A tenth type, mixed, is the deliberate catch-all: no prescribed stages, just the project root.

Each stage stays in its own job and hands off to the next when its work is done, so the agent never sprawls across the whole project at once.

blockchain: an example stage map

projects/[name]/
├── research/     summarize findings, flag risks
├── contracts/    Solidity reviewer
├── frontend/     dApp frontend reviewer
├── deploy/       track deployed contracts, verify state
└── audit/        adversarial reviewer, find exploits

Every other typed vertical follows the same shape: a role per stage (e.g. client-work's intake is "understand before promising", learning's practice is "hands on keyboard, not eyes on videos"), a "done" artifact, and an explicit move-on condition (e.g. cli-tool's spec stage moves to core/ once the command surface is locked).

mixed: the catch-all

Selectable when nothing else fits. Just the project root, no prescribed stages. You add structure as the project grows, and the zones still give you capture, queue, and focus from day one.

See also: Getting Started · The Zones · Contributing.