Series
Agent-ready React
A six-part series on making legacy React codebases ready for AI coding agents.
6 parts · first published
- 01
Why Your Legacy React Codebase Confuses AI Coding Agents
AI agents stumble on mature codebases because they have accreted multiple valid answers to the same question — and an agent has no way to know which one is current.
· 7 min read - 02
A 3-Week Plan to Make Your Legacy React Codebase Agent-Ready
Three weeks, one engineer, one opinionated order. Stop the drift, collapse the duplicates, and let the rules you already have actually start working.
· 12 min read - 03
Rules That Agents Actually Follow: Enforcement Over Aspiration
A perfectly written CLAUDE.md cannot fix a contradictory codebase. The most effective rules file is short, opinionated, and backed by tooling.
· 12 min read - 04
What to Put in design.md: A Complete Template
A good design.md is a decision document, not a style guide. If a senior designer left tomorrow, would the next person make the same calls?
· 14 min read - 05
Writing Task-Specific Agent Prompts That Work First Try
If design.md is the agent's memory, task prompts are its muscle memory — the highest-leverage agentic asset you can build, and the most underused.
· 12 min read - 06
Session-Start Hooks That Pay for Themselves
Zero ongoing cost. Measurable improvement on every interaction. The underused feature of modern coding agents — what to put in it, and what not to.
· 13 min read