← all skills

vercel-deploy

• Web
• operative — changes the codebase
• 268 lines
• 4 references

Ship a Next.js 16 App Router project to production on Vercel end-to-end: preview → smoke test → a *staged* production deployment (vercel --prod --skip-domain) that serves no traffic yet → vercel promote → domains and DNS, plus a rollback runbook. Requires stack.framework in {next, monorepo} and phase >= feature_complete; sets phase = "deployed" on success. Idempotent. Triggers on: "deploy", "ship it", "go live", "push to production", "manda in produzione", "attacca il dominio", "rollback the deploy". Not for: the Vercel project config — vercel.json, region, env-var matrix, monorepo root directory are module-add deploy (run it first); the pre-deploy gates (vercel-doctor, compliance-audit, shadscan); CI and git hooks (module-add ci); an Expo/RN app (rn-eas-deploy); an eve agent (eve deploy).