A Claude Code starter template for building any application — structured, phase-driven, stack-agnostic.
Binary is a GitHub template repo that gives developers a structured workflow for building apps with Claude Code. It handles the process — requirements, architecture, phases, testing — so you focus on building.
Who it's for: Developers who know their stack but want an opinionated Claude Code workflow.
- Click Use this template on GitHub
- Open your new repo in Claude Code
- Run
/check— Claude reads your project state and tells you the next step - Follow the guided flow from requirements to deployment
- Copy
/convertto~/.claude/commands/convert.md(one-time global install) - Open your existing repo in Claude Code
- Run
/convert— fetches latest Binary files, drops workflow on top, offers to restructure code
| Command | What it does |
|---|---|
/check |
Snapshot — current phase, what's done, what's next |
/next |
Resume — continues current task or advances to the next one |
/add |
Add a new app to code/ — Claude asks questions, gives you setup commands |
/test |
Run full regression suite across all apps |
/done |
Mark current task or phase complete |
/convert |
Install Binary workflow into an existing repo (global command) |
Requirements → Architecture → Phases → Build → Test → Deploy
/checkshows empty requirements → Claude grills you until docs are filled- Docs complete → Claude auto-generates phases in
todo/ /nextfrom any state — mid-task, new task, or new phase — always resumes correctly- Each phase includes tests;
/testruns everything, every time progress.mdis Claude's memory — updated after every task, never stale
docs/ — requirements, architecture, decisions (filled before any code)
code/ — one subfolder per app (api/, web/, worker/, ...)
todo/ — phase files, auto-generated after design docs complete
tests/ — registry.md (master test list) + reports/ (e2e output)
progress.md — Claude's session memory, auto-updated
AGENTS.md — workflow rules for Claude (read this)
- Never writes code before requirements and architecture docs are filled
- One branch per phase:
feature/phase-N-<name> - One commit per task, immediately after completion
- No new packages without discussion
- Updates
progress.mdafter every meaningful action
/add can be run multiple times. Each app gets its own folder inside code/. Tests live co-located with each app. tests/registry.md tracks what's covered across the whole project.
Open source. Built by Epyc.