From vercel
Installs Vercel CLI, authenticates, links the current project, and reviews environment variables.
How this command is triggered — by the user, by Claude, or both
Slash command
/vercel:setupThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Vercel Setup 1. Check/install Vercel CLI (`npm install -g vercel`) 2. Authenticate with `vercel login` 3. Link project with `vercel link` 4. Review environment variables with `vercel env ls`
npm install -g vercel)vercel loginvercel linkvercel env lsnpx claudepluginhub antimatter15/claude-plugins-official --plugin vercel/deployDeploys the current project to Vercel, defaulting to a preview deployment or production when "prod" or "production" is passed. Includes preflight checks for uncommitted changes and observability readiness.
/studio-env-setupGuides users through transferring local OAuth credentials to Cloudflare, Vercel, or Netlify for Nuxt Studio authentication.
/cloudflare-deployDeploys Cloudflare Worker project to production, staging, or preview environments with wrangler, including pre-deployment checks, secrets management, and dry-run option.
/workers-deployDeploys Cloudflare Workers with environment selection, pre-deploy validation (tests, types, build), and safety checks. Supports --env flag for direct environment targeting.
/setupInitializes or resumes Conductor project setup by creating foundational documentation (product definition, tech stack, workflow, style guides) through interactive Q&A.
/setupChecks whether the local Codex CLI is ready and optionally toggles the stop-time review gate. If Codex is not installed, prompts the user to install it via npm.