AI Prompting Hits a Subtraction Moment: Anthropic Deletes 80% of Its Own Rules
The rule-stuffing playbook that dominated prompt engineering for two years is now counterproductive. Developers who keep piling constraints and capability skills onto frontier models are paying more for worse output, while those who strip down to private business knowledge get better results at lower cost.
Anthropic's July 24 update for Opus 5 and Fable 5 stripped away the vast majority of Claude Code's system instructions without any performance regression. The official line: too many constraints restrict a model's judgment and degrade output. The same logic applies to user-land CLAUDE.md files and skill libraries — Databricks research found that expanding a skill library to 202 entries caused a 21% drop in task pass rates, not because of context limits but because the model picked the wrong tool.
The dividing line is now clear. Skills that teach AI how to work — planning, task decomposition — are dead weight that frontier models handle natively. Skills that encode private knowledge — company definitions, test commands, business logic — retain their value and should be loaded on demand. A new built-in /doctor command even audits your configuration and suggests cuts.
Separately, Kimi K3's full 2.8T-parameter weights landed on Hugging Face, ranking third globally on the Artificial Analysis index behind only Claude Fable 5 and GPT-5.6. Cloud providers including Alibaba, Volcano Engine, and Tencent already host it, sidestepping the official subscription shortage. Meanwhile, OpenAI's Codex has removed its 5-hour paid-tier cap and now runs GPT-5.6 with lenient ban policies, making it a more stable entry point than Claude Code for newcomers facing Anthropic's 1.45 million account bans and 3.3% appeal success rate.
Anthropic publicly admitting its own system prompts were 80% waste and shipping a tool to delete user configs is an unusually self-aware move that resets the entire prompt-engineering conversation.
The skill-library finding — that failure comes from selection errors, not context overflow — means the problem is cognitive load on the model, not token budgets, which changes how developers should think about tool integration.
Kimi K3's open weights combined with immediate multi-cloud availability creates a pricing and access dynamic that proprietary API-only models cannot match, even if the raw benchmark is slightly lower.
The reasoning-tier benchmark inversion — where medium outperforms max — suggests frontier models now suffer from an overthinking pathology that wastes both time and money on simple tasks.