Ship It Checklist

Checklists /Cursor or Claude Code, Next.js and Vercel /Deploy

High

Run the production build before you invite users

next dev forgives errors that next build refuses. The usual ones are a missing module, a client hook in a server component, and a page that reads cookies while it is being rendered statically. If the Vercel build is red, there is no production app.

How to check

  1. On a clean install, run the production build command the same way Vercel will.
  2. Read the first error, not the last line of the log.
  3. Open the Vercel deployment and confirm the latest production deployment is ready.
  4. Load the production URL, not only localhost.

Prompt

Fix prompt
Paste into Cursor or Claude Code
You are working in this repository. Do not add features.

Goal: the production build completes.

Steps:
1. Run the project build and read the first error.
2. If a module is missing, add the dependency that the import needs, or remove the unused import. Do not add a pile of unrelated packages.
3. If a client hook is used in a server component, add "use client" only on the component that needs it, or move the hook out.
4. If Next.js reports dynamic server usage because of cookies or headers, read them in the request path and await the call, rather than inside setTimeout.
5. Tell me the command you ran and the result. Do not disable type checks to hide the error.

This uses the same ticks as the checklist page, saved in this browser.

Related error fixes