Debugging Flow

Your feature works – now make sure it's solid before (and after) you ship. Most problems come down to the same few checks, and Claude can run them and fix what it finds. This is the loop to reach for whenever something breaks.

The whole loop, in one move

Type check → fix · Lint → fix · Build → fix. Claude often does this on its own, but it's worth knowing – running these three in order clears the large majority of issues.

1. Run the fix-it loop

Ask Claude to run the three checks in order and fix as it goes.

Check types, lint, and build – and fix everything
Run my project's checks and fix what you find, in this order:
1.Check for TypeScript errors and fix them.
2.Check for lint errors and fix them.
3.Run the production build and fix any remaining errors or warnings.
Make minimal, safe edits (don't reach for `any` or broad refactors), re-run each check until it's clean, and show me a short summary of what you changed.

Outcome: Types, lint, and the production build are all clean.

Claude cleared my type, lint, and build issues

2. Ship it and verify in production

Commit, push to main, and verify the live site
Let's ship the feature:
1.Commit my work with a clear message and push it to main so Vercel deploys it.
2.Check the latest Vercel deployment, summarize any warnings or errors, and tell me when it's Ready.
3.Give me a short checklist to test the live site on desktop and mobile (UI, the feature's logic, loading/error states).
The one bug that only shows up live

The most common problem that appears in production but not on your machine is a missing environment variable on Vercel – your app works locally but the deployed version can't reach a service because its key isn't set. You'll learn how environment keys are managed (stored on Vercel, pulled down locally) when you set up your database in the next level. For now, just remember: if it works locally but breaks live, check your Vercel environment variables first.

Outcome: Your feature is deployed and verified live in production.

I shipped my feature and verified it live in production