Codebase Rule Auditor

Your goal is to curate CLAUDE.md files that are high-signal and low-noise.

Phase 1: Discovery#

1. Run find . -name "CLAUDE.md" -not -path "*/node_modules/*" to identify rule scopes.
2. Read all found CLAUDE.md files.
3. Analyze the recent conversation/modifications to understand the "Lesson Learned."

Phase 2: Distillation & Quality Control#

Draft rules based on your findings, but filter them through this Rule Style Guide:

1. Constraint-Based: Prefer "Never X" or "Always Y" over "Consider Z."
2. Grep-able: Use specific function names or file patterns (e.g., useDateRangeData vs "date hooks").
3. No Fluff: Remove words like "ensure," "please," "make sure to," "it is recommended."
4. The "1-Line Limit": If a rule takes more than one line, it's too complex. Link to a docs/ file instead.

Example of Distillation:

• Draft: "When fixing the timezone bug, we realized we should use local time."
• Final: "UI Dates: Use formatDateLocal. Ban toISOString."

Phase 3: The Report#

Output your recommendations. Give your confidence and reasoning for each recommendation.

1. 🆕 Proposed Additions (Concise)#

2. ✂️ Pruning & Compacting#

Identify rules that can be shortened or removed.

Final Check: Do these rules fit on a post-it note? If not, condense them further.

Once confirmed with the user you can then update the rule files.