---
name: deploy-to-vercel-checklist
description: "A deploy checklist for Vercel covering environment variables, build settings, domains and preview checks, so a launch does not fail on a missed setting. Use when a project is about to be deployed to Vercel and needs build, environment, domain and preview checks confirmed first. Do not use for debugging a failing build log or comparing hosting providers. Related topics: devops, coding."
---

# Deploy to Vercel Checklist

A deploy checklist for Vercel covering environment variables, build settings, domains and preview checks, so a launch does not fail on a missed setting.

## When to use

Use this skill when a project is about to be deployed to Vercel and needs build, environment, domain and preview checks confirmed first. Do not use it for debugging a failing build log or comparing hosting providers.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Confirm the build group: preset, root directory, commands, output directory and runtime version match the repository.
3. List every environment variable name with its scopes and mark the ones exposed to the browser, flagging secrets with public prefixes.
4. Check the domain group: DNS, redirects, HTTPS and which branch is production.
5. Write the verification steps to run on the preview URL and the rollback test.
6. Finish with a go or no-go line naming whatever still blocks launch.

## Inputs

- **Framework** (free text, e.g. "Next.js or Vite or Astro or other")
- **Repository layout** (choose one: Single app, Monorepo, Static site)
- **Environment variables** (longer free text)
- **Custom domain** (free text, e.g. "Domain or none")
- **Backend dependencies** (longer free text)
- **Release type** (choose one: First deploy, Routine release, Migration from another host)

## Output

A four-group checklist (Build, Environment, Domains, Verification) with checkboxes, a variable scope table, and a final go or no-go line.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Deploy to Vercel Checklist

Prepare this project for a Vercel deploy.

- Framework: {{Framework}}
- Repository layout: {{Repository layout}}
- Environment variables: {{Environment variables}}
- Custom domain: {{Custom domain}}
- Backend dependencies: {{Backend dependencies}}
- Release type: {{Release type}}

Produce a checklist in four groups. Build: confirm the framework preset, root directory for monorepos, install and build commands, output directory and Node version. Environment: for each variable name, say which scopes need it (Production, Preview, Development), mark which are exposed to the browser, and flag any that look like secrets sitting in a public prefix. Domains: DNS records, redirect from www or apex, HTTPS and the production branch. Verification: open the preview URL, test one logged-in path, check serverless function logs, confirm cron and webhook URLs point at the right host, and test a rollback by promoting the previous deployment. Never request the values of secrets, only their names. Add a go or no-go line at the end listing what blocks launch.

## Pitfalls

- Setting a variable only for Production, so preview deployments break with confusing errors.
- Putting a secret key behind a browser-exposed prefix, which publishes it in the client bundle.
- Forgetting the root directory in a monorepo, so the build succeeds on the wrong package.