Playbooks & production notes

Maintainability

How to keep an AI-built codebase understandable, testable, and safe to change as prompts, features, contributors, and production pressure accumulate.

Keeping an AI-built codebase readable and safe to change as features, prompts, and contributors pile up. For founders who can feel every edit getting slower than the last. Start with "Why Your AI App Gets Harder to Change Every Week", then "CLAUDE.md Best Practices".

All Launch Readiness Security Data Safety Stability Deployment Performance Revenue Maintainability

24 playbooks

Best AI Code Reviewer: Who Says So, and What It Can Actually Read

Can AI Do Code Reviews? What It Catches and What It Cannot See

You Paid a Developer and the App Is Half Finished: What to Do Next

Hiring a Developer to Take Over Your Project: Four Checks

What Is a Code Review? What Actually Happens, Step by Step

Code Review as a Service for AI Code: What It Costs and Who Sells It

Should You Rebuild Your Vibe Coded App or Fix It? Run the Numbers First

How to Clean Up a Vibe-Coded App: Six Steps That Do Not Break It

What a Vibe Coding Cleanup Actually Costs

Documentation for a Vibe-Coded App: The Complete Set

Inherited a Vibe-Coded App? First-Week Triage

What a Vibe Coding Cleanup Specialist Actually Fixes, Ranked by How Often It Was Needed

What to Give a Developer Taking Over Your Vibe-Coded App

Migrate From Lovable to Claude Code: The Editor Moves, the App Does Not

Claude Code YOLO Mode (--dangerously-skip-permissions): How to Skip Permissions Safely

How Much Does It Cost to Hire an App Developer for an AI-Built App

Cline Rules Examples: Guard the Paths That Break

Cursor Rules Best Practices: Types, Globs, and Examples