Prod down? Don't fix it — roll back

Prod down? Don't fix it — roll back 1. Vercel → Deployments → Instant Rollback. The previous version comes back in seconds. 2. Walk through the customer journey: login, form, payment. 3. Find the error in the logs or an alert, copy the whole line. 4. Give it to Claude Code with the prompt below. 5. Fix → preview → check → prod. Prompt (tap to copy):

You are an experienced developer. Help me work out why my site crashed in production. Context: the site runs on [your stack, e.g. Next.js], hosting [Vercel], services [e.g. Convex, Resend]. What broke: [what the user sees]. Error: [paste the entire line from the logs or alert]. What changed: [what you changed in the last deploy]. Rules: 1) Don't change anything at first — only read the code, config and logs. 2) Name the most likely cause and prove it: which file, which line, which variable. 3) Name 2 more possible causes in case the first one isn't confirmed. 4) Suggest a minimal fix, no refactoring. 5) Tell me how to test the fix on a preview before releasing to prod. Response format: Cause → Evidence → Fix → How to verify. Use simple words.

The key part of the prompt is "don't change anything until you've explained it." That way Claude won't break what's still working. And don't deploy on a Friday evening 🙃