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 Compliance Stability Deployment Performance Revenue Maintainability

73 playbooks

API error handling best practices: one error shape, accurate status codes, one boundary, and no failure that looks like success

The email bounce handling checklist for an app: provider webhooks, the suppression list, and keeping your sending reputation

Email rate limit exceeded: which sending limit you hit, and how to raise it

Email verification email template: what it says, HTML that renders everywhere, and the page the link lands on

How to add a frontend error boundary and a global backend handler: no blank white screen, no unexplained 500

How to improve email deliverability for the email your app sends: three controls, one test each

How to run long tasks in the background: moving AI generation, exports and bulk email off the request

How to send verification email and password reset email from your app, and what to check when a customer never gets one

How to stop email spoofing: keeping anyone from sending mail as your domain, and what DNS cannot fix

How to test email deliverability before launch: the tools, what each one checks, and what a pass looks like

An idempotency key for safe retries, and a dead letter queue: jobs that run once and failures you can replay

SPF DKIM DMARC setup for the domain your app sends from: add the three records, then prove they pass

Stack traces are minified and unreadable: error tracking with private source maps, environment labels and alerts that mean something

Transactional email best practices for an app: a dedicated provider, the messages that must arrive, and proof each one did

Transactional emails landing in spam: how to find which of four causes you have, and get back to the inbox

What is a health check endpoint? Readiness, degraded status, and what it must never expose

What is chaos testing? Outage drills in staging: simulating an AI or payment provider failure before customers depend on the fallback

What is exponential backoff: retries that wait longer each time, stop at a limit, and never charge a customer twice