eval-rules

# 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 | Mechanism | When it loads | Notes | |---|---|---| | `@file` in CLAUDE.md | Session start, always | Even inside a conditional sentence | | No `paths:` in rule | Session start, always | Same cost as @import | | `paths:` frontmatter | When Claude reads a matching file | Trigger = Read tool on a matched file | | User-level rule (`~/.claude/rules/`) | Session start, always | Applies to all projects on the machine | The `paths:` field is the main lever for keeping rules contextual. An always-on rule with 80 lines loads on every session even if you're fixing a typo in README.md. Glob patterns in `paths:` support brace expansion: `"src/**/*.{ts,tsx}"` matches both `.ts` and `.tsx` files with one entry. --- ## Scoring Criteria (12 pts per rule) | # | Criterion | Max | What is checked | |---|-----------|-----|-----------------| | 1 | **frontmatter block** | 1 | File has ...