Rules Evaluator

Discover all rule files, validate their structure and glob patterns against the real project, then run an interactive session to confirm (or improve) each rule with the user.

The goal is not just to score — it is to leave the rules directory in better shape than it was.

When to Use

• First time writing .claude/rules/ files (validate before committing)
• A rule seems to never trigger, or fires on every file
• Migrating @ imports from CLAUDE.md to path-scoped rules
• Periodic hygiene: "are these rules still relevant to how we work?"
• After onboarding to a new codebase

Key Concepts