Recipes

Short checklists for the changes people make most often after cloning the template. Each page lists the files to touch in order, the commands to run, and what fails if you skip a step. They are written so you, or the coding agent you are steering, can follow them literally.

Run ./verify.sh at the end of every recipe:

./verify.sh   # repo root, after npm ci in backend/ AND frontend/

For a whole new feature (its own table, service and routes), use Adding a Module instead. For a new tool on the admin MCP server, see Admin MCP Server.

Pages

1. Add a field to an existing table
2. Add a page
3. Gate a feature behind a subscription
4. Add a backoffice screen
5. Send an email
6. Rebrand

Related

• Home - Docs index
• Architecture - How the two halves fit together