The new rules of context engineering for Claude 5 generation models
Thariq Shihipar, a member of technical staff at Anthropic, explains how context engineering for Claude Code has changed with Claude 5-generation models. The old playbook—hard rules, examples, everything upfront, repeated instructions, CLAUDE.md as memory, and simple markdown specs—is now partly myth. New guidance: let the model use judgement (the system prompt now says 'match the surrounding code' instead of banning multiline comments); design expressive tool interfaces instead of stuffing examples; adopt progressive disclosure by loading verification and review skills on demand and letting tools defer their definitions until ToolSearch finds them. CLAUDE.md should stay lightweight, holding repo-specific gotchas, while skills encode team-specific opinions. Specs can become rich references: HTML mockups, test suites, code to port, or rubrics with verifier agents. Anthropic also ships `claude doctor` to auto-simplify contexts. No benchmarks are included, and the article is vendor-authored, but it offers immediately actionable patterns for agent harness and Claude Code users.