Deploy to Vercel Checklist skill for Claude and Codex

Deploy to Vercel Checklist as an AI skill. It asks for Framework, Repository layout, Environment variables and 3 more, then does the rest. Free to install in…

Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.

Download the skill (.zip) · View SKILL.md

When it is used

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.

What it will ask you for

• 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)

How it works

1. Confirm the build group: preset, root directory, commands, output directory and runtime version match the repository.
2. List every environment variable name with its scopes and mark the ones exposed to the browser, flagging secrets with public prefixes.
3. Check the domain group: DNS, redirects, HTTPS and which branch is production.
4. Write the verification steps to run on the preview URL and the rollback test.
5. Finish with a go or no-go line naming whatever still blocks launch.

What you get

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

What it watches out for

• 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.

How to install

Claude.ai and the Claude desktop app

1. Download the skill .zip.
2. Open Settings, then Capabilities, and find Skills.
3. Choose Upload skill and select the .zip.
4. Ask Claude for help with the task. It loads the skill when your request matches.

Claude Code

1. Download the skill .zip.
2. Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
3. Start a new session. Claude Code loads the skill when your request matches.

Codex

1. Download the skill .zip.
2. Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
3. Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.

Cursor

1. Download the Cursor rule (.mdc).
2. Save it in .cursor/rules/ inside your project.
3. Cursor's agent applies the rule when your request matches its description.

AGENTS.md (Codex, Cursor, and other coding agents)

1. Copy the AGENTS.md section.
2. Paste it into AGENTS.md at the root of your repository, creating the file if needed.
3. Coding agents that read AGENTS.md follow it when your request fits.