Downloads · free · no sign-up
2 things you can use without talking to me.
The rules I give Claude Code before it touches an n8n instance, and the template I write handover docs to. Plain text: take them and change them.
-
Starter kit · zip
n8n + Claude Code house rules and starter kit
The house rules Claude Code follows in every client repo. It builds on a dev instance only, and a human promotes to production. Send nodes never carry recipients, workflows stay under 15 nodes, and no secret is hardcoded. Plus the per-client template: Claude gets a key to the dev instance only, workflow deletion is switched off, and production activation waits behind a y/N prompt.
- house-rules.md
- README.md
- CLAUDE.md
- PROGRESS.md
- new-client.sh
- deploy.sh
- .mcp.json.example
- docker-compose.yml.example
- .gitignore
Not included: Part A, the upstream prompt from the n8n-MCP project the rules sit on top of, and any env file.
-
Template · Markdown
Automation handover doc: the 11-section template
The standard: an engineer who didn’t build it can deploy, run, fix and change it, from the doc alone. 11 sections in 2 to 4 pages: what it does, the system map, configuration, the routine cycle, routine changes, failure modes, deploy from zero, access, boundaries, who owns what, and the change log. It ends with a 6-question self-audit.
Status: none of the 3 docs I have delivered has yet had a dry run by someone who didn’t build the system. This is the standard I write to, not a proven result.