Shipping to Vercel or Netlify in one command

You have a built project. A static site, a Next.js app, an SPA. It's ready to go live. The deployment part should take two minutes but instead it takes thirty — configuring the platform, setting environment variables, figuring out the build command, choosing the right framework preset, clicking through the dashboard.

The /deploy skill handles this. One command. It detects the project type, picks the right configuration, deploys, and hands you a live URL.

What it handles

Project detection — Reads the project to determine what you've got: static HTML, Next.js, React SPA, Vue, Astro, or generic Node.js. Sets the build command, output directory, and framework configuration automatically.

Platform routing — Two sub-skills: vercel-deployer and netlify-deployer. Each knows the platform's CLI, configuration format, and deployment model. You say where you want it; the skill handles the rest.

Environment variables — If the project has a .env.example or .env.local, the skill identifies which variables need to be set on the platform and prompts you before deploying.

Build verification — Runs the build locally first. If the build fails, you get the error before the deploy attempt, not after a three-minute upload and remote build that produces the same error.

The two paths

Vercel — Uses the Vercel CLI. Handles project linking, environment configuration, framework detection, and deployment. Supports preview deployments and production deployments. References references/vercel-guide.md for platform-specific configuration details.

Netlify — Uses the Netlify CLI. Handles site creation, build configuration, redirect rules, and deployment. Supports draft and production URLs. References references/netlify-guide.md for platform specifics.

Both produce a live URL at the end.

When to use it

Every time you deploy. That's the point. The command is faster than the dashboard.

For preview deployments. Ship a branch to a preview URL, share it with the team, iterate, then promote to production.

For new projects. First deployment of a new project requires the most configuration. The skill handles the setup so subsequent deploys are even faster.

Skip it if you have a CI/CD pipeline that already handles deployment on push. This skill is for manual, intentional deploys — not continuous deployment.

---

Resources

Skill reference: /deploy — trigger phrases, platform options, sub-skills.

Related reading:

• 08. Building a landing page from a codebase — build the page, then deploy it
• 07. How much does your infrastructure actually cost at scale? — understand hosting costs before choosing a platform

Download: Full toolkit (252KB) — all 16 commands, all 11 skills, installs in 30 seconds.

---

Part of the Claude Skills Library.