Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-03-21 · source-backed
A 380-upvote r/ClaudeAI thread documents a failure mode that every Claude Code power user has experienced but few have articulated this clearly: as CLAUDE.md grows from 45 to 190 lines, Claude ignores more rules, not fewer. The instruction file becomes noise.
The author's fix wasn't writing better instructions. It was replacing instructions with code. Hook scripts that assert state before commits. Test runners that enforce patterns programmatically. Automated checks that fail loudly rather than relying on the model to remember paragraph 47 of a behavioral spec. The principle: code is a more reliable instruction mechanism than behavioral prose, and past ~100 lines, CLAUDE.md becomes a net negative.
This consolidates a pattern that's been emerging for weeks. The r/ClaudeAI thread (115 comments) shows broad practitioner consensus: the developers getting the best results from Claude Code aren't the ones with the most comprehensive instruction files. They're the ones who've built verification infrastructure that makes compliance checkable rather than requestable.
The analogy that keeps surfacing in the thread is unit testing. Nobody writes a comment saying "please don't break the login flow" — they write a test that fails if the login flow breaks. CLAUDE.md rules should work the same way: if a rule matters enough to write down, it matters enough to enforce with a hook, a test, or a structured output schema.
There's also a related finding from a 64-upvote post documenting a mandatory python -m pre_output_check execution step injected into Claude Code's output style section, claiming approximately 50% hallucination reduction. The pattern is the same: move from "please do X" to "X will be verified before output."
The actionable takeaway: audit your CLAUDE.md. If it's over 100 lines, start converting rules to hooks, tests, and verification scripts. The instruction file should be a thin behavioral layer on top of mechanical enforcement, not a substitute for it.
Each link below shares sources, entities, or timing with this story.
Claude Code uses MCP / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Claude Code uses MCP); both cover Claude, Claude Code, ClaudeAI, There; reported by the same outlet (reddit.com).
Claude Code uses Opus / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Claude Code uses Opus); both cover Claude Code, ClaudeAI, Test, There; reported by the same outlet (reddit.com).
Uber uses Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Uber uses Claude Code); both cover CLAUDE, Claude Code, ClaudeAI; reported by the same outlet (reddit.com).
Linked by a graph relationship (Uber uses Claude Code); both cover Claude, Claude Code, ClaudeAI; reported by the same outlet (reddit.com).
Claude Code uses Opus / Shared entities / Same source domain / What happened next
Linked by a graph relationship (Claude Code uses Opus); both cover Claude Code, ClaudeAI, Nobody, There; reported by the same outlet (reddit.com).
Claude Code uses MCP / Shared entities / Same source domain / Shared topic / What happened next / Tension
Linked by a graph relationship (Claude Code uses MCP); both cover CLAUDE, ClaudeAI; reported by the same outlet (reddit.com).
Anthropic released Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Anthropic released Claude Code); both cover Claude, Claude Code, ClaudeAI; reported by the same outlet (reddit.com).
Microsoft criticizes Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Microsoft criticizes Claude Code); both cover CLAUDE, Claude Code, ClaudeAI; reported by the same outlet (reddit.com).