Vercel CLI expert for serverless deployment. Use when users need to deploy apps, manage domains, env vars, or Vercel projects.
/plugin marketplace add leobrival/topographic-studio-plugins/plugin install dev@topographic-plugins-officialThis skill inherits all available tools. When active, it can use any tool Claude has access to.
reference/commands-reference.mdreference/common-patterns.mdreference/troubleshooting.mdVercel is a serverless platform for deploying, scaling, and managing web applications. This guide provides essential workflows and quick references for common Vercel operations.
# Check Vercel CLI installation
vercel --version
# Authenticate with Vercel
vercel login
# Show current user
vercel whoami
# Link project to Vercel
vercel link
# Pull environment variables
vercel env pull .env.local
# Initialize new project
vercel init
# Or link existing project
vercel link
# Start local development
vercel dev
# Create preview deployment
vercel
# Deploy to production
vercel --prod
# List all environment variables
vercel env ls
# Add new variable
vercel env add API_KEY
# Pull variables to .env.local
vercel env pull .env.local
# Start dev with environment
vercel dev
# Add domain to project
vercel domains add example.com my-project
# Verify domain configuration
vercel domains inspect example.com
# Check DNS records
vercel dns ls example.com
# List all deployments
vercel list
# View deployment logs
vercel logs https://my-app-xyz.vercel.app
# Follow logs in real-time
vercel logs --follow https://my-app-xyz.vercel.app
# Inspect deployment details
vercel inspect https://my-app-xyz.vercel.app
# View recent deployments
vercel list
# Rollback to previous version
vercel rollback https://my-app.vercel.app
# Redeploy if needed
vercel redeploy https://my-app.vercel.app
When to use which command:
vercel devvercel (no flags)vercel --prodvercel env add/rm/lsvercel domains add/inspectvercel logs [url]vercel rollback [url]# 1. Setup environment variables
vercel env add API_KEY
vercel env add DATABASE_URL
# 2. Test locally
vercel dev
# 3. Create preview
vercel
# 4. Test preview URL
# ... verify at https://my-app-xyz.vercel.app ...
# 5. Promote to production
vercel promote https://my-app-xyz.vercel.app
# 6. Monitor production
vercel logs --follow https://my-app.vercel.app
# Switch to team
vercel switch my-team
# Pull team project settings
vercel pull
# Deploy to team project
vercel --scope my-team --prod
# Deploy to multiple regions
vercel --regions sfo1,fra1,sin1
# In vercel.json:
{
"regions": ["sfo1", "fra1"]
}
# Deploy via CI/CD pipeline
vercel --token $VERCEL_TOKEN --prod --yes
# Build and deploy
vercel build
vercel --prebuilt --token $VERCEL_TOKEN
Common Issues:
Cannot login
vercel --token $TOKEN whoamiProject not linked
vercel link to link projectBuild fails during deployment
vercel build locally to debugDeployment crashes after build
vercel logs https://my-app.vercel.appDomain not resolving
For detailed troubleshooting steps, see the Troubleshooting Guide.
Load as needed for detailed information:
Commands Reference - Complete CLI command documentation with all flags and options. Use when you need exact syntax or flag details for any Vercel command.
Common Patterns - Real-world patterns and workflows for development, deployments, domains, environment management, debugging, team collaboration, and production setups. Use for implementing specific workflows or integrations.
Troubleshooting Guide - Detailed error messages, diagnosis steps, and resolution strategies for authentication, deployment, runtime, domain, git integration, and environment variable issues. Use when encountering errors or unexpected behavior.
When to use each reference:
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.