Start from a template. Make it yours.
Seven setups worth copying. Pick one, switch things on and off, and the
.cpb file writes itself, live. Apply it with one command.
Credentials stay references; nothing in the file is a secret.
The gallery
Seven setups, each a plain .cpb file
Each one is a recipe: it names no playbook, so you apply it to whichever one you like. Read it, customize it, or take it as it is.
The customizer
Switch things on and off. The file follows.
Everything on the right is generated by the same code that CI runs against a real cpb, for every template and a large set of combinations. It only writes what cpb accepts.
How it works
From a file to a running Claude Code
- 1
Get the file
Copy or download it from the customizer, or fetch a template as it is:
curl -fsSL /p/code-reviewer.cpb -o reviewer.cpb - 2
Read it, then check it
A recipe is plain statements.
--dry-runshows every change and command before anything is written.cpb APPLY reviewer.cpb TO review --dry-run - 3
Apply it
Applying twice changes nothing. The playbook gets its own command; run it like any other.
cpb APPLY reviewer.cpb TO review
Secrets are references
A GitHub token appears as FROM 'keychain:github-mcp', resolved at launch by your secret helper. The customizer refuses anything that looks like a credential, and so does cpb.
A sandbox is a creation flag
SANDBOX and NO PILOT PROFILE are set when the playbook is created, so a recipe cannot carry them. In recipe form the customizer puts them on the cpb CREATE PLAYBOOK line; in file form they are in the file.
Same code, tested
The files in /p/ and every option combination are applied by a real cpb in CI. If a template stops working, the build fails, not your afternoon.