Start a Claude Code project with guard rails that hold. One command seeds a new repo with hooks that block secrets and dangerous commands before the model’s intent matters, a CLAUDE.md whose rules are anchored to real incidents, ten focused reviewers, and twenty skills.
$ bash /path/to/claude-blueprint/seed.sh .
| No. | Component | Count | Remark |
|---|---|---|---|
| 01 | Bash hooks, .claude/hooks/ | 8 | Secrets and dangerous commands blocked before the tool call runs |
| 02 | Coding rules, .claude/rules/ | 15 | Path-scoped — they cost nothing until you touch matching files |
| 03 | Focused reviewers, .claude/agents/ | 10 | Security, silent failures, performance, docs, data, frontend, PR tests |
| 04 | Skills, .claude/skills/ | 17 + 3 | ship · tdd · debug-fix · pr-review · incident-rule · and more |
| 05 | Engineering rules with incidents | 9 | Each one paid for — docs/RULES.md names what broke and what it cost |
The core fails closed (it blocks if jq is missing). Convenience hooks fail open, so they never get in your way.
You wrote “write clean code” and the model ignored it — because the rule describes a feeling, not a situation. There is no moment where the model can tell it is about to break it. A rule that wins names the exact moment, the exact wrong move, and what it cost.
“Don’t rewrite things unnecessarily.”
A mood, not an instruction. No recognisable moment, no cost, nothing to trigger on.
“Never replace a whole list to add one item. If an API looks like it can only replace, read its input schema before you believe that. On 2026-08-12 a project board’s status options were replaced twice to add one option each time. Both times the platform silently dropped all 63 card assignments. The input type had an id field the whole time.”
Names the moment, the wrong move, and the cost. All nine rules ship with the dated incident behind them.
Take the plugin for the machinery — hooks included. Take seed.sh when you want the rules too, as files you own and can edit. seed.sh never overwrites an existing CLAUDE.md, .gitignore or .env.example.
# everything, as files you own
git clone https://github.com/eugnmueller-87/claude-blueprint.git
cd my-new-project
bash ../claude-blueprint/seed.sh .
# then: fill in CLAUDE.md, cp .env.example .env, git init
# hooks, reviewers and skills — rules and CLAUDE.md stay with seed.sh
/plugin marketplace add eugnmueller-87/claude-blueprint
# a hard-coded key should be blocked (exit 2); a clean env-var reference allowed (exit 0)
echo '{"tool_name":"Write","tool_input":{...}}' | bash .claude/hooks/scan-secrets.sh
“A rule without an incident will not be merged. If it never hurt, it does not earn context space.”