Devbook
The rules, templates and prompts for building real software with AI coding assistants. Spec first, small steps, verified output.
What this is
Section titled “What this is”Devbook is the set of standards I follow on every project, written so that both a person and an AI agent can follow them. Each page is a short list of rules with the reason behind them, not an essay.
It has three layers. Universal rules apply to every project whatever the stack. Stack profiles add the specifics for a tool such as Astro, Cloudflare or Django. Project docs live in each project’s own repo and hold only what is unique to it.
Start hereHow the devbook is organised and how to adopt it in a project.
LLM-assisted workflowBrief, spec, plan, small tasks, verify, review. The loop behind every change.
SecurityBaseline rules, supply chain, LLM application risks and privacy.
Web & contentTechnical SEO, structured data, people-first content and evidence.
TemplatesAGENTS.md, project brief, technical spec, ADR and more.
PromptsCopy-paste prompts for planning, building, reviewing and auditing.
How to read a rule
Section titled “How to read a rule”- MUST / MUST NOT: required. Breaking it needs a written decision record in the project.
- SHOULD / SHOULD NOT: the default. Deviate when you have a reason, and write the reason down.
- MAY: optional.
Pages about fast-changing tools show a “Last verified” date. Treat older dates as a prompt to check the vendor’s current docs.