CLAUDE.md Is RAM, Not Disk

What it is — An argument for treating CLAUDE.md as small, constantly-loaded working memory, and pushing everything else into a docs/ folder that’s only pulled in on demand.

Key points

• CLAUDE.md loads into every session and costs tokens every time, so keep it to a short project overview, pinned stack/versions, exact commands, and one-line pointers — not exhaustive detail.
• Move deeper material into docs/ (architecture in DESIGN.md, a phased roadmap in PLAN.md, a lightweight decision log in DECISIONS.md) referenced only when needed.
• Nested, folder-level CLAUDE.md files keep domain-specific rules local instead of bloating the root file.