Opus 4.7 Broke 40% of Prompts; Fix Was Structuring CLAUDE.md and Skills

When Opus 4.7 dropped in April, about 40% of the prompts across 6 mid-market company setups broke overnight. Token burn went up, outputs became weirdly literal — 4.6 had been filling in ambiguous instructions, but 4.7 didn't. The fix wasn't rewriting prompts; it was finally taking CLAUDE.md and Skill files seriously.
What broke and why
Prompts written for 4.6 assumed the model would be charitable about vague instructions. 4.7 interpreted them literally, causing outputs that needed 3-4 turns to correct. Prompts that survived were those baked into Skill files with explicit output formats, length caps, and worked examples.
The rebuild approach
Across the 6 setups, three structural changes were made:
- Skills replaced standalone prompts — anything done more than 3 times got a Skill file (50–200 lines) with audience, output format, length, and a 2-3 sentence worked example. Skills are loaded on demand instead of bloating context.
- Hierarchical CLAUDE.md — one global file for user identity, business, voice rules; a project-level CLAUDE.md per engagement; session-level instructions for one-offs. Model reads in order and builds a mental model that survives across sessions.
- Memory files broken out — kept CLAUDE.md under 400 lines; detailed institutional knowledge lives in separate files that CLAUDE.md points to, loaded on demand.
- Verification step in long Skills — model generates output, checks against a 5–7 item checklist, revises. Adds 30s per call but cut downstream cleanup ~70%.
Results after 3 weeks
- Average prompt-to-acceptable-output dropped from 3-4 turns to 1-2.
- Token usage dropped 22% across workspaces.
- "This output is weird, let me try again" rate dropped from once per 4 prompts to once per 15.
- Next model release should now be a net positive, not net negative.
Still unsolved: versioning CLAUDE.md
Project-level files are in git, but the global CLAUDE.md lives in chat history, which is fragile. No rollback mechanism yet.
Mental model
The model is the engine. Skills + CLAUDE.md + memory is the car. Build the car once; each new engine makes it faster.
📖 Read the full source: r/ClaudeAI
👀 See Also

Analysis of Claude Code's Production Engineering Patterns from Reverse-Engineered Source
A developer reverse-engineered approximately 500,000 lines of Claude Code's TypeScript source code into a 19-chapter technical handbook documenting production engineering patterns that emerge under real load, real money, and real adversaries.

How to set up Qwen 3.6 Plus Preview on OpenRouter for free OpenClaw usage
Qwen 3.6 Plus Preview is currently free on OpenRouter with a 1 million token context window, suitable for AI agent work. The setup involves creating an OpenRouter account, adding the provider to OpenClaw, and configuring the model.

OpenClaw setup guide from Reddit analysis: hardware, cost, memory, and security practices
A Reddit user analyzed common OpenClaw mistakes and created a setup guide covering hardware requirements, cost optimization to $10/month, memory management using MEMORY.md files, and security practices to prevent prompt injection attacks.

Setting Up MCP Servers in llama-server Web UI: A Practical Guide
A Reddit user shares specific steps to configure MCP servers in llama-server's web UI, including installing uv, creating a config.json file with server definitions, running mcp-proxy, and modifying URLs for proper integration.