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
Why Your OpenClaw Scheduled/Cronjob Tasks Fail
When you ask an agent to create a scheduled task, it often creates a shell or Python script instead of using OpenClaw's prompt-in-cron feature. This makes tasks non-agentic and inefficient.
Automating Claude Session Restarts with tmux and at
Use tmux and the at command to schedule automatic restarts of your Claude session when usage resets at odd hours.
Spent $850 on OpenClaw in One Month? Fix Your Architecture, Not Your Model
A developer burned $850 in a month on OpenClaw multi-agent setup — with $350 gone in a single day. The fix wasn't a cheaper model — it was system design: strict context pruning, session resets, n8n for non-reasoning tasks, and a routing tier for cheap vs. strong models.
Reducing MCP token usage by replacing servers with CLI alternatives
A developer found that MCP servers were consuming 30-40% of their context window with tool definitions, so they replaced four MCP servers with CLI tools where available, reducing from 6 to 2 MCP servers while maintaining functionality.