Fetching from the wire…
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.
For a month, Claude Code users were convinced the model had been "nerfed." Forums lit up. Conspiracy theories multiplied. People switched tools. Then on April 23, Anthropic did something unusual: they published a detailed post-mortem that named three specific bugs with exact d...
New model doesn't mean better model. The r/ClaudeAI community learned this the hard way. The top post on r/ClaudeAI hit 2,757 upvotes with 682 comments calling Opus 4.7 "a serious regression, not an upgrade." Cross-platform sentiment was uniformly negative: 818 upvotes on r/si...
A Reddit post about giving Claude Code a cheap coworker hit 1,123 upvotes and 115 comments on r/ClaudeAI. Read together with the Uber story above, this is the demand signal paired with its solution. The setup: route routine implementation work to a $0.02/call model (Gemini Fla...
Go open your CLAUDE.md. Count the instances of "must" and "never." A reader on r/ClaudeAI did exactly that after Anthropic's September 8 platform post and found 66 of one and 54 of the other across their rule files. Their complaint wasn't the count. It was that they couldn't t...
805 upvotes. 255 comments. The highest-engagement story on r/ClaudeAI yesterday. A developer ran /loop before bed and burned approximately $6,000 in Claude usage by morning. I use /loop regularly. This story hit home. The problem isn't that /loop is dangerous. It's that there'...
Steve Yegge built a Go-based multi-agent orchestrator called Gas Town that ran 20 to 30 parallel Claude Code instances. It worked. Then it didn't. His postmortem, surfaced by Simon Willison on August 4, is blunt: Gas Town "fell apart at the seams with Opus 4.7. Up through 4.6...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.