5 CLAUDE.md Mistakes Everyone Makes

You set up a CLAUDE.md. Good. But is it actually helping? Here are the five mistakes I see constantly.

Mistake 1: Too Long

If your CLAUDE.md is 500+ lines, Claude Code is spending tokens reading your novel instead of doing work. Keep it under 200 lines. Be ruthless about what's essential.

Mistake 2: Too Vague

"Use good coding practices" tells Claude nothing. "Use TypeScript strict mode, Tailwind for styling, and put components in src/components/" tells it everything. Be specific. Be opinionated.

Mistake 3: No Session Lifecycle

The most valuable section of CLAUDE.md is the session lifecycle — what to read at start, what to write at end. Without it, you lose the memory system entirely.

Mistake 4: No Communication Preferences

Tell Claude Code HOW to talk to you. "Be direct. No preamble. Code first, explanation after. Don't ask if I want you to proceed — just do it." This saves hundreds of back-and-forth messages.

Mistake 5: Never Updating It

Your CLAUDE.md should evolve. When Claude makes a mistake you've corrected before, add it to CLAUDE.md. When you discover a pattern that works, document it. A living CLAUDE.md gets more powerful every week.

The Quick Fix

Open your CLAUDE.md right now. Check:

• Under 200 lines?
• Specific stack and conventions listed?
• Session lifecycle defined?
• Communication preferences included?
• Updated in the last week?

If any answer is no, spend 10 minutes fixing it. Your next 100 sessions will thank you.