Has Claude Code Been Nerfed? The Truth Behind the Perception
I dropped $100 on a Claude Pro subscription last month, and within weeks, I was convinced: Claude Code had been nerfed.
Tasks that used to take one prompt now required three. Code suggestions felt shallow. The model seemed to “shortcut” through complex problems instead of thinking them through. I found myself re-explaining context that Claude should have remembered.
So I did what any frustrated developer would do—I went looking for evidence.
The “Nerf” Theory Spreads
Turns out I wasn’t alone. A growing thread on r/claude was filled with similar complaints:
User A: "Claude used to nail my React components. Now it misses basic imports."
User B: "I swear Medium effort feels like Low effort now."
User C: "aiDailyCheck shows quality dropping. It's real."The aiDailyCheck metric kept coming up—a user-run benchmark tracking perceived quality over time. The charts showed dips. The comments section lit up with “confirmed nerf” takes.
But something felt off. The evidence was all perception-based. No one had actual capability metrics. No one could point to a changelog or announcement.
So I dug deeper.
What’s Actually Happening
I started experimenting with the same tasks across different configurations. Same prompts, same codebase, different setups.
Experiment 1: Default CLAUDE.md vs Optimized CLAUDE.md
My original CLAUDE.md was a mess—2,400 lines of accumulated rules, examples, and edge cases accumulated over months of “just add this one thing.”
Result with bloated CLAUDE.md:- Claude missed context- Suggestions were generic- Required 2-3 clarification rounds
Result with reorganized CLAUDE.md (400 lines, progressive disclosure):- Context was remembered- Suggestions were specific- One-shot success rate: ~80%Experiment 2: Medium vs High Effort
The effort setting was another culprit. I’d gotten lazy, defaulting to Medium for everything.
Medium effort, complex refactoring:- Quick surface analysis- Missed edge cases- "Shortcutting" behavior
High effort, same task:- Deep context gathering- Caught edge cases- Thorough implementationThe pattern emerged: the model wasn’t degraded—my workflow was.
The Real Culprits
Three factors created the “nerf” perception:
1. Context Bloat
My CLAUDE.md had become a dumping ground. Every new requirement, every edge case, every “remember this” got appended. The model wasn’t ignoring me—it was overwhelmed.
The fix? Progressive disclosure:
Before (everything at once):├── All coding rules├── All testing rules├── All deployment rules└── All edge cases (200+ items)
After (layered disclosure):├── Core principles (always loaded)├── Domain-specific rules (loaded per project type)└── Edge cases (loaded only when triggered)2. Effort Setting Mismatch
Medium effort isn’t a bug—it’s a feature for fast iteration. But I was using it for tasks requiring deep analysis.
Task complexity vs Effort level:
Low complexity (formatting, simple edits):└── Medium effort: perfect match
Medium complexity (feature additions):└── Medium effort: 60% success└── High effort: 90% success
High complexity (refactoring, architecture):└── Medium effort: 30% success└── High effort: 85% success3. Growing Codebase Complexity
My project had grown. More files, more dependencies, more implicit knowledge. What used to be a “simple” request now required navigating a more complex context.
The model didn’t get worse—the task got harder.
The Optimization That Changed Everything
I spent a weekend restructuring my entire AI workflow. Here’s what I changed:
CLAUDE.md Restructure:
# Core Principles (always apply)- Immutability first- Error handling always- Validate inputs
# Domain Rules (conditional)- Frontend: component patterns- Backend: API patterns- Database: query patterns
# Triggered Rules (only when relevant)- Specific library quirks- Edge cases from past failuresEffort Strategy:
Default: Medium (for iteration speed)
Upgrade to High when:- Architecture decisions- Complex refactoring- Multi-file changes- Security-critical codeContext Hygiene:
Weekly audit:- Remove stale rules- Consolidate duplicates- Archive resolved edge casesThe result? My one-shot success rate jumped from ~40% to ~75%. The “nerf” disappeared.
Why This Matters
Before assuming AI degradation:
- Audit your prompts—are they clear?
- Check your context—is it focused or bloated?
- Match effort level to task complexity
- Consider whether your project has grown
The difference between “nerfed” and “needs optimization” often comes down to configuration, not capability.
Common Mistakes to Avoid
- Mistake 1: Blaming the model without checking setup
- Mistake 2: Using Medium effort for complex tasks
- Mistake 3: Letting CLAUDE.md grow unchecked
- Mistake 4: Not testing with different configurations
- Mistake 5: Trusting perception metrics over controlled experiments
How to Diagnose Your Setup
Run this quick test:
- Take a task Claude “failed” on recently
- Move your CLAUDE.md to a backup
- Create a minimal CLAUDE.md with just core rules
- Retry the task with High effort
- Compare results
If step 4 works better, your issue isn’t the model—it’s the configuration.
The Bigger Picture
AI assistants are tools, not magic. They respond to how they’re configured. When results degrade:
- The tool might have changed
- The task might have grown harder
- The configuration might need updating
All three are fixable. But only if you look for the real cause.
Summary
In this post, I investigated whether Claude Code has been nerfed. After controlled experiments, I found three real culprits: context bloat, effort setting mismatch, and growing codebase complexity. The optimization—restructuring CLAUDE.md, matching effort to task complexity, and weekly context audits—restored my success rate from ~40% to ~75%. The key insight: before assuming AI degradation, audit your configuration. The difference between “nerfed” and “needs optimization” often comes down to how you’ve set up your AI assistant.
Final Words + More Resources
My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me
Here are also the most important links from this article along with some further resources that will help you in this scope:
Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!
Comments