
5 CLAUDE.md Patterns That Actually Work in Production
Everyone's talking about AI coding agents. Most people are still writing CLAUDE.md files that look like this: Use TypeScript. Follow best practices. Be helpful. That's a style guide, not a system prompt. Here are 5 patterns I've tested in production that actually change how the agent behaves. 1. Constrained Autonomy The biggest unlock wasn't giving the agent more freedom. It was defining exactly where the fence is. ## Constrained Autonomy ### Do without asking: - Code formatting, lint fixes - Running tests - Commits and pushes (within scope) - Installing dependencies (one auto-retry on failure) - Research, analysis, reports - Drafting marketing content ### Ask first: - Releases, version changes - Anything that costs money - Security-impacting changes - Bulk operations (5+ PRs/Issues — show count, then confirm) - Direct production impact - Major strategy pivots Why this works: the agent stops asking permission for trivial stuff, but you still have a kill switch on anything expensive or
Continue reading on Dev.to
Opens in a new tab



