A rulebook my team’s Claude follows
One set of rules every engineer’s Claude reads in every repo, with checks that hold them before every push and merge request.
The problem
Each engineer’s Claude kept its own rules, so the team’s lessons drifted apart and fixed bugs came back.
What I built
- 150+ rules for frontend, backend, design and QA, each with its reason and the bug that taught it.
- Rules harvested from each teammate’s own corrections, tickets and design decisions.
- A rule broken twice becomes a check: a gate before every push, and CI on every merge request.
- Every merge request carries a stamp that the check ran.
In numbers
- 150+
team rules, each with its reason
- 250+
commits since 26 Oct 2026
- 4
areas: frontend, backend, design, QA
Stack
Claude Code pluginHooks and skillsGitLab CIBash
Want something like this? Tell me about your project or hire me on Upwork.