Thanks for your interest in contributing! This collection stays intentionally small — every rule must solve a real problem that people actually hit in production.
- New rules that solve a universal problem across Claude Code projects (not project-specific configuration)
- Improvements to existing rules based on real-world experience
- Bug reports when a rule causes unintended agent behavior
- Project-specific rules (put those in your own
.claude/rules/) - Rules that duplicate Claude Code's built-in behavior
- "Nice to have" guidance that doesn't prevent concrete problems
- Rules longer than 80 lines — if it can't be said concisely, it's too complex for an always-on rule
- Fork the repo
- Create a branch:
git checkout -b rule/your-rule-name - Add your rule to
rules/using the template intemplates/RULE.md.template - Write a clear PR description explaining:
- What problem does this solve?
- How did you discover this problem? (real scenario)
- How did you verify the rule works? (tested with Claude Code)
- Submit the PR
- Solves a real, recurring problem (not hypothetical)
- Under 80 lines (agents read this every session)
- Uses bold keywords for scannability
- Includes anti-patterns section
- Tested with actual Claude Code sessions
- Works as always-on OR has correct path-scoping globs