D
daemonstack
← back to community
#claude.md#workflow

How do I keep CLAUDE.md growing with my project without it becoming a mess?

3/5/2026 Β· status: open

I started using CLAUDE.md about 3 weeks ago. It was simple at first (10 lines), but today it's around 200 lines and I'm noticing: - Some sections became dead text (Claude ignores them) - Others conflict with each other (one says "use Tailwind", another says "use CSS modules") - I'm afraid to cut things thinking they don't matter and break something How do you keep CLAUDE.md as a LIVING document? Do you have a review cadence (weekly, monthly)? Who decides what stays/goes? Is it worth splitting into smaller files (CLAUDE.md + @architecture.md + @workflows.md)? Project stack: Next.js + TypeScript + Supabase. Team of 3 devs.

0 answers

No answers yet.

Sign in to answer.