Companion template
The skeleton so you do not invent structure on day one.
The kit is a foundation, not an application. Create a repository from the template. Fill the placeholders. Follow Day One. If the repo already has code, do not pretend Day One already happened.
What ships in the template
- CLAUDE.md and AGENTS.md — standing instructions the Build-space agent reads every session.
- DAY_ONE.md — ordered first-session script for a new repo.
- EXISTING_PROJECT.md — assess a repo that already has code. Attach kit files as context. Do not merge first.
- PROJECT_INSTRUCTIONS_STARTER.md — one-pager for Design-space project knowledge.
- Docs tree that already obeys location-carries-status, plus brief / INV / ADR / runbook / progress templates.
- Path-scoped rules, review skills, PR template, CI hard gate, example deploy workflow.
- Migration folder convention and a load-bearing test-isolation example.
Starter packets
Three copy-ready document packets live next to the template: expense tracker, price watcher, email planner. Briefs, ADRs, investigations, runbooks, hand-offs. No application source. You copy them in after Day One.
Launch fulfilment can be a zip while the public template repo is being published. Buyers get the same files either way.