Playbooks & production notes

Stability

Reliability practices for finding silent failures, handling third-party errors, keeping useful logs, and recovering an AI-built app.

Silent failures, third-party errors, logs that say nothing useful, and the outages a founder hears about from a customer first. For anyone running an AI-built app without an on-call rotation. Start with "When Your App Fails Silently and Says 200 OK", then "Why Your App Works Locally but Not in Production".

All Launch Readiness Security Data Safety Stability Deployment Performance Revenue Maintainability

12 playbooks

Stability

App Crashes After Publishing to the Store: Six Release Differences

My Tests Pass But the App Is Still Broken

Fix My Base44 App: What Breaks, and Who Can Fix Each Part

Fix My Lovable App: What to Do When the Fix Loop Stops Working

Do You Need a Status Page for a Small SaaS?

App Broke After an AI Edit? What Actually Changed

Dependency Update Broke My App? Recover Without Guessing

Fix AI Generated Code: What to Do When the AI Cannot Fix It

Error Logging Best Practices for a Solo AI-Built App

Uptime Monitoring for Founders: Do You Need It Yet?

Why Your App Works Locally but Not in Production

When Your App Fails Silently and Says 200 OK