Stats
Actions
Tags
From vercel
Installs Vercel CLI globally via npm if needed, authenticates account, links current project, and lists environment variables for review.
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 joshuarweaver/cascade-code-devops-misc-1 --plugin vercel-vercel-deploy-claude-code-plugin/deployDeploys current project to Vercel via CLI with preflight checks. Defaults to preview; pass 'prod' or 'production' for production with explicit confirmation.
/studio-env-setupInteractively guides OAuth env var setup for Nuxt Studio on Cloudflare Pages/Workers, Vercel, or Netlify. Detects local config first, no args needed.
/cloudflare-deployDeploys Cloudflare Worker project to production, staging, or preview environments with wrangler, including pre-deployment checks, secrets management, and dry-run option.
/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex, Bedrock, Foundry, or gateway), producing a customized manifest.xml for M365 deployment.