Free stuff 0417.10.2026
Production is down: prompt and checklist.
Claude CodeVercelCheckly[From an @levizdev reel]
What to do when your site breaks after a deploy: roll back first, then find the error and hand it to Claude Code so it explains the cause before touching anything.
01/ Prompt
You are a senior developer. Help me investigate a production outage.
Context: the site runs on [your stack, e.g. Next.js], hosted on [Vercel], services [e.g. Convex, Resend].
What broke: [what users see, e.g. the lead form doesn't submit].
Error: [paste the full line from the logs or the alert].
What changed: [what you added or changed in the last deploy].
Rules:
1) Don't change anything yet — 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 doesn't hold.
4) Propose the smallest possible fix, no refactoring.
5) Tell me how to verify the fix on a preview deployment before shipping to production.
Answer format: Cause → Evidence → Fix → How to verify. Use plain language.
03/ How to run
- 01Don't fix — roll back. Vercel → Deployments → Instant Rollback (or vercel rollback in the terminal). The previous version is back within seconds. On the free Hobby plan you can only roll back to the previous production deployment.
- 02Check the site is alive: walk the customer path — login, form, checkout.
- 03Find the error: the monitoring alert (e.g. Checkly) plus Vercel logs. Copy the full error line.
- 04Hand the error to Claude Code with the prompt above — cause first, then the fix.
- 05Fix → preview deployment → check → production. And don't deploy on Friday evening.
Why it worked
Prompt formula.
01ContextStack, hosting and services — otherwise Claude has to guess where to look.
02What brokeThe symptom as the customer sees it.
03ErrorThe exact line from the logs or the alert, not a summary.
04What changedThe last deploy — that's where the cause usually is.
05RulesThe key one: change nothing until you've explained. That keeps Claude from breaking what still works.
06Answer formatCause → evidence → fix → verification. You can tell at once whether it understood the problem or is guessing.
Open for projects
Need a detail like this on your site?
The prompt is a good start. If it has to live inside a real site, connect to sign-up and be production-ready, I'll build it end-to-end.