How to Write a CLAUDE.md (or Cursor Rules) That Actually Works
Your AI assistant used the wrong framework? Here's how to write instruction files (CLAUDE.md, Cursor Rules) that actually prevent that.
Configuring AI Coding Assistants for Large Codebases
A 6-part series on writing instruction files, managing context, and enforcing architecture rules for AI coding assistants like Claude Code and Cursor.
6 parts
Part 1
Part 2
Why Your AI Coding Assistant Ignores Half Your Instructions
Extra instructions don't help. They hurt. Learn to scope AI instruction files so your assistant only sees what matters for the current task.
Part 3
AI Writes Code That Compiles but Breaks Your Architecture: Here's Why
When AI takes architectural shortcuts your code still compiles, but breaks in production. Document the decisions AI can't infer from code alone.
Part 4
Why AI Hallucinates Imports (and How to Stop It)
The mechanics behind phantom packages, version drift, and cross-module confusion, plus concrete prevention strategies for large codebases.
Part 5
How to Give AI Assistants a Map of Your Messy Codebase
Monorepos, legacy migrations, mixed framework versions. Here's how to configure AI coding assistants when your codebase doesn't follow one set of rules.
Part 6
AI Follows Your Instructions 70% of the Time: How to Enforce the Rest
AI instruction files work 70% of the time. Close the gap with hooks, automated validation, and team governance strategies.