We Audited Our Claude Code Setup Against Anthropic's Own Context-Engineering Rules — Here's What We Found

The question that started this

We run Claude Code against a fairly large, fairly automated repository — a farming-assistance platform with a Node.js backend, a Flutter app, a React dashboard, an in-progress Spring Boot microservices migration, and a home-grown "repo memory" layer called gps that captures invariants, lessons, and preferences across sessions. Over several months we'd wired up a lot of automation: session-start hooks, prompt-submit hooks, auto-captured preferences, persona plugins, a mandatory agent-dispatch table. It felt sophisticated. It also felt, some days, slow to get going — every session seemed to start with a wall of text before any real work happened.

So when Anthropic published "The New Rules of Context Engineering for Claude 5 Generation Models", we asked the obvious question: are we actually following our own advice, or have we just accumulated automation that looks like good practice?

This post is the audit, the root cause we found, and the fix — including a mistake we made mid-fix that's worth telling on ourselves for.

What the blog post actually says