Fetching from the wire…
Public story · 2026-07-25 · high
The company says examples now hurt Claude 5 models instead of helping, upending a year of prompt engineering habits.
Why now: Anthropic tied this reversal to Opus 5's launch, which is the model teams are rewriting their CLAUDE.md files for right now.
Anthropic deleted more than 80% of Claude Code's system prompt for its Claude 5 generation models. The company reported no measurable loss on coding evaluations, per its post on context engineering, published on Opus 5's launch day.
For anyone maintaining a CLAUDE.md or AGENTS.md file, that means most of what's in there was built to compensate for a model that's already retired.
The more disruptive claim is about examples. Anthropic says giving the new models few-shot examples "constrains them to a certain exploration space," and recommends designing expressive tool interfaces instead.
Few-shotting has been standard practice since GPT-3. Anthropic is telling people to stop.
Anthropic's CLAUDE.md advice: keep it lightweight, say what the repo is for, and spend most tokens on codebase gotchas, not hard behavioral rules. Their example swap replaces "Never write multi-paragraph docstrings" with guidance to match the surrounding code's idiom and comment density.
paddo.dev corroborated the 80% figure with a cost number. One build dropped from 470k tokens ($1.29) on Opus 4.8 to 179k tokens ($0.33) on Opus 5. That's a 62% token cut and a 74% cost cut on identical work.
paddo.dev also audited 74 real CLAUDE.md files hunting for the "verify your work" instructions Anthropic says to cut, and found zero genuine self-check imperatives. Every "verify" hit was domain vocabulary, JWT checks, HMAC signatures, or an external command like running flutter analyze. A blind grep for that word would have broken all 74 repos.
My own project rules file has eighteen months of "Claude keeps doing X, stop it" entries. I couldn't tell you which ones a Claude 5 model still needs.
paddo.dev's fix: split permanent repo facts from perishable model patches, and review the second pile at every model release. I'm adopting it. Don't grep your rules file, read it.
Each link below shares sources, entities, or timing with this story.
For two years the technique was accumulation. Longer system prompts, longer CLAUDE.md, more numbered do/don't lists, more "always verify your work" imperatives. Anthropic's context-engineering guidance for Claude 5 models inverts it, with an 80% deletion figure attached. The s...
This one changed how I'm spending my week. Anthropic's July 24 context-engineering post says they removed over 80% of Claude Code's system prompt for Opus 5 and Fable 5 with no measurable loss on coding evals. They call it "unhobbling" — stripping guardrails and rules that new...
DeepClaude hit 470 points on Hacker News. It swaps Claude Code's API backend to DeepSeek V4 Pro while preserving the full agent loop: file editing, bash execution, git tooling, the whole workflow. DeepSeek V4 Pro scores 96.4% on LiveCodeBench at a fraction of Anthropic's prici...
This is the install-this-today story. code-review-graph (3.5K GitHub stars) builds a persistent AST-based knowledge graph of your codebase using Tree-sitter, then queries it at review time to compute the minimal context set Claude actually needs. On a 27,732-file Next.js monor...
This is the most useful thing I read this week and it isn't close. Anthropic published its internal methodology for running large-scale code migrations with Claude Code on July 16, and unlike most engineering-blog playbooks, it carries receipts. Bun's Zig→Rust migration: rough...
43.3% on Frontier-Bench v0.1. Opus 4.8 scored 18.7%. That's not an incremental bump, that's the same benchmark with a different shape of answer. Anthropic released Claude Opus 5 on July 24 at $5/$25 per million input/output tokens, exactly half of Fable 5's $10/$50, while matc...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.