How to Prevent CLAUDE.md Rot: Treat Rules Like Code
After running Claude Code on production projects for 18 months, u/mm_cm_m_km identified the single most common failure point: the CLAUDE.md file rots. Not because Claude ignores it, but because developers keep adding rules without ever cleaning them up. The result is a bloated 500-line file that costs tokens every turn and drifts out of sync with the actual codebase.
1. CLAUDE.md as an Index, Not a Manual
Keep CLAUDE.md to 30–50 lines. It should act as a table of contents pointing to specific files for specific concerns — not a wall of every preference you have ever set. Claude rereads the file on every turn; short files are cheap, long files waste tokens and attention.
2. Every Section Answers One of Two Questions
- What behavior do you want? (the rule) — belongs in
CLAUDE.md. - Where do you find the current truth? (the source) — belongs as a fetchable URL or file path Claude can re-read at task time.
Mixing rules and sources is how files grow without bound. Keep the rule short, the source external.
3. Audit Before Merge, Not After
Rules silently drift as you rename things, refactor hooks, or drop features. The fix is not "be more careful" — it is a CI step. The author built a GitHub App called agentlint (agentlint.net) that audits the rules surface on every PR: contradictions across files, references to deleted paths, rules describing harness features your version does not support.
4. Delete More Than You Add
Almost every CLAUDE.md gains one new rule per week and deletes zero. After six months you have a Frankenstein. The discipline: for every new rule, find one to delete. This has kept the author's file under 100 lines.
The core pattern: treat your rules surface like code. Code has tests, review, and drift detection. Rules need the same.
📖 Read the full source: r/ClaudeAI
👀 See Also
Browser Agents Ate My API Budget: The Hidden Cost of Observation Loops
Running AI agents on real web tasks? A Reddit user reports that browser observation loops — not the model — are the dominant cost driver. Every click, wait, and observe triggers a round trip, and poor snapshot quality creates a compounding failure spiral that inflates token usage. Isolated browser environments and faster agent execution are key cost-saving measures.
Loading Every MCP Server on Every Prompt Quietly Destroys Token Budget
A user with 5–6 MCP servers found each prompt loaded all servers, causing massive token waste. Implementing a routing layer to load only relevant servers per prompt drastically reduced token usage and improved response times.
Claude Isn't Bad at Coding — Your Context Setup Is
After months of using Claude, one developer argues failures stem from how you structure context, not the model itself. Key improvements: separate instructions from logic, cut context noise, and use stable patterns.
Building a Developer Portfolio with Claude Code: A Junior Dev's Workflow and Lessons Learned
A 21-year-old junior MERN stack dev shares how he built nidhil.live using Claude Code, emphasizing the importance of specific prompting and understanding generated code instead of blind copy-pasting.