How to Use It Well
Use these rules as a working agreement. Keep the active set small, and add a short checklist at the top: tests first, small diffs, stop early.
Adoption Checklist
- Start with one real task and keep the scope narrow
- Capture a baseline: time-to-first-success and output quality
- Version your config/skills so teammates stay in sync
Guardrails
Rules are only useful when enforced. Pair them with CI gates (tests, lint) and code review conventions.
FAQ
Q: Is this copyrighted book content? A: The README states the rules are inspired by books and intentionally avoid reproducing book text; treat them as operational instructions.
Q: Which variant should I start with?
A: Use mini for most tasks; keep nano for tight context budgets and full as reference.
Q: How do I combine multiple books? A: Start with one baseline (e.g., Refactoring), then layer a second only after you see consistent behavior.