/guardrail

Generate custom lint rules that enforce architectural decisions at edit time.

Philosophy

Lint rules are the highest-leverage codification target. They're cheaper than hooks (no custom Python), more durable than CLAUDE.md (automated, not advisory), and work in CI too (not just Claude Code). A lint rule catches violations the moment code is written — and fast-feedback.py surfaces the error immediately so Claude self-corrects.

When to Use

• Import boundaries ("all DB access through repository layer")
• API conventions ("routes must start with /api/v1")
• Deprecated pattern blocking ("no direct fetch, use apiClient")
• Auth enforcement ("handlers must call requireAuth")
• Naming conventions that go beyond basic linting