Anthropic overhauls Claude's context engineering and system prompts

Anthropic's system prompt for Claude Code used to read like a rulebook: hard constraints and exhaustive examples meant to keep older, weaker models from going off the rails ^[1]. With Claude Opus 5 and Claude Fable 5, the company deleted more than 80 percent of that prompt and measured no drop in coding evaluation scores ^[1][2]. The reasoning runs almost opposite to intuition: rigid examples end up constraining a model that turns out to be more imaginative than the examples it's given, so instead of prescribing exact behavior, Anthropic now tells Claude to use judgment - for instance, matching the comment density, naming, and idioms of the surrounding code rather than following a fixed style rule ^[1]. Thariq Shihipar, the Claude Code engineer behind the change, called it part of a broader evolution in how the team writes prompts, driven by a simple insight: examples meant to guide the model end up constraining it, because the model is more imaginative than the examples it's given ^[2].

The mechanism behind the cut is progressive disclosure: rather than loading every rule into context at the start of a session, Claude Code now fetches guidance just-in-time. Verification and code review, for example, used to live inline in the system prompt; they've been moved into their own on-demand skills that Claude selectively calls only when it needs them ^[1]. The upside is less crowded context and fewer conflicting instructions - guardrails written for older model behavior no longer sit permanently in the prompt, competing for attention with more relevant guidance ^[1]. Independent commentator Mager frames this as "unhobbling" Claude - stripping away safeguards that compensated for older model limitations but now create friction: "The harness that was necessary last year is friction this year." The same critique extends to how developers write their own CLAUDE.md files: teams carrying heavy, rule-laden documentation are effectively carrying technical debt under the new guidance ^[3].

A detail that didn't make Anthropic's blog post but surfaced in public discussion of the change is that the company no longer runs one universal system prompt across its whole model lineup. Newer, more capable models like Opus 5 and Fable 5 get the pared-down prompt; older or smaller models keep the fuller, more prescriptive legacy prompt they still need. Prompt length is effectively now versioned by capability tier rather than fixed once and reused everywhere - a tacit acknowledgment that a single system prompt applied uniformly was itself part of the overconstraining problem Anthropic says it's correcting.

The reception hasn't been uniformly celebratory. In the days after the post went up, discussion communities pushed back that the "80 percent" headline describes a cut to a specific behavioral-rules segment of the prompt, not the entire context Claude Code loads, and some readers suspected the framing was doing more work than the underlying change warranted. There were also early reports of the opposite failure mode - a model following custom instructions too literally once extra scaffolding was removed, which is exactly the risk Cat Wu flagged when she said prompt authors need to think adversarially about how a leaner instruction "could be misinterpreted by a well-intentioned human" ^[4]. The tension points to a real tradeoff: fewer rules reduce "context rot," the degradation Anthropic's applied AI team first named when it formally defined context engineering as curating the optimal token set during inference ^[5], but they also remove the explicit backstops that used to catch edge cases a model hadn't yet learned to handle on its own. On X, reaction to the change echoed the same reframing, with commentators describing it less as a prompt shrinkage and more as a broader shift from writing prompts to designing context.