Zero-auth Vercel deployment workflow with automatic framework detection for 20+ frameworks. Use when deploying web applications to Vercel, creating preview deployments, or setting up deployment pipelines. Supports Next.js, Vite, Remix, SvelteKit, Astro, Nuxt, and more.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Zero-auth Vercel deployment workflow with automatic framework detection for 20+ frameworks. Use when deploying web applications to Vercel, creating preview deployments, or setting up deployment pipelines. Supports Next.js, Vite, Remix, SvelteKit, Astro, Nuxt, and more.
Zero-auth deployment to Vercel with automatic framework detection. Deploy any web application with a single command and receive preview URLs, claim URLs, and deployment metadata.
When to Apply
Use this skill when:
Deploying a web application to Vercel for preview or production
Setting up a deployment pipeline for a new project
Creating preview deployments for pull request review
Testing production builds in a live environment
Demonstrating a prototype or proof of concept
Supported Frameworks
Vercel auto-detects and configures builds for these frameworks:
Framework
Detection
Build Command
Next.js
next.config.*
next build
Vite
vite.config.*
vite build
Remix
remix.config.*
remix build
SvelteKit
svelte.config.*
vite build
Astro
astro.config.*
astro build
Nuxt
nuxt.config.*
nuxt build
Gatsby
gatsby-config.*
gatsby build
Angular
angular.json
ng build
Vue CLI
vue.config.*
vue-cli-service build
Create React App
react-scripts in deps
react-scripts build
Ember
ember-cli-build.js
ember build
Hugo
config.toml / hugo.toml
hugo
Jekyll
_config.yml
jekyll build
Eleventy
.eleventy.js
eleventy
Docusaurus
docusaurus.config.*
docusaurus build
Static HTML
index.html at root
None
Deployment Workflow
Step 1: Prerequisites
Ensure the Vercel CLI is installed:
# Install globally
npm install -g vercel
# Or use npx (no install needed)
npx vercel
Step 2: Project Setup (First Time Only)
For new projects not yet linked to Vercel:
# Interactive setup -- creates .vercel/project.json
vercel link# Or create a new project
vercel --yes
Step 3: Deploy
Preview Deployment (Default)
# Deploy to preview environment
vercel
# Output:# Vercel CLI 34.x.x# Linked to username/project-name# Inspect: https://vercel.com/username/project-name/abcdef# Preview: https://project-name-abc123.vercel.app
Production Deployment
# Deploy to production
vercel --prod
# Output includes production URL:# Production: https://project-name.vercel.app
Zero-Auth Deployment (Agent Mode)
For automated deployments without authentication prompts:
# Using VERCEL_TOKEN environment variable
VERCEL_TOKEN=your-token vercel --yes --token=$VERCEL_TOKEN# Or with npx for zero-install
VERCEL_TOKEN=your-token npx vercel --yes --token=$VERCEL_TOKEN
# Check deployment status
vercel inspect <deployment-url>
# View deployment logs
vercel logs <deployment-url>
# List recent deployments
vercel list
Configuration Options
Environment Variables
# Set environment variables for deployment
vercel env add VARIABLE_NAME production
vercel env add VARIABLE_NAME preview
vercel env add VARIABLE_NAME development
# Or pass inline
vercel -e KEY=value -e KEY2=value2
Build Configuration
Override auto-detected settings in vercel.json:
{"buildCommand":"npm run build","outputDirectory":"dist","installCommand":"npm install","framework":"vite","rewrites":[{"source":"/(.*)","destination":"/index.html"}]}
Custom Domains
# Add a custom domain
vercel domains add example.com
# Assign domain to project
vercel alias <deployment-url> example.com
ALWAYS test the build locally before deploying to ensure the deployment will succeed
NEVER deploy to production without first creating and validating a preview deployment
ALWAYS verify environment variables are configured in the Vercel project before deploying
NEVER store sensitive secrets in deployment commands or public URLs
ALWAYS check the deployment logs immediately after deployment to confirm the build succeeded
Anti-Patterns
Anti-Pattern
Why It Fails
Correct Approach
Deploying without local build test
Build fails in Vercel, wasted deployment attempt
Run build locally before vercel deploy
Skipping preview before production
Regressions reach users before detection
Always validate preview URL first
Hardcoded env vars in deploy command
Secrets exposed in shell history and logs
Configure env vars in Vercel project settings
Ignoring post-deploy build logs
Silent failures go undetected
Always check logs after deployment
No framework detection verification
Wrong settings cause build failures
Verify auto-detected framework in project config
Framework Detection Patterns
Vercel CLI auto-detects frameworks by checking project files in this priority order:
Framework
Detection File
Build Command
Output Dir
Next.js
next.config.*
next build
.next
Remix
remix.config.*
remix build
build
SvelteKit
svelte.config.*
vite build
build
Astro
astro.config.*
astro build
dist
Nuxt
nuxt.config.*
nuxt build
.output
Vite
vite.config.*
vite build
dist
Gatsby
gatsby-config.*
gatsby build
public
Angular
angular.json
ng build
dist
Vue CLI
vue.config.*
vue-cli-service build
dist
Create React App
react-scripts in pkg
react-scripts build
build
Docusaurus
docusaurus.config.*
docusaurus build
build
Eleventy
.eleventy.js
eleventy
_site
Hugo
config.toml (Hugo)
hugo
public
Jekyll
_config.yml (Jekyll)
jekyll build
_site
Static HTML
index.html only
none
.
When auto-detection fails, specify framework explicitly:
vercel --build-env FRAMEWORK_PRESET=nextjs
Environment Variable Management
Setting Environment Variables
# Add env var (prompts for value)
vercel env add MY_VAR production
# Add from .env file
vercel env pull .env.local
# List all env vars
vercel envls# Remove env var
vercel envrm MY_VAR production
vercel teams ls# List teams
vercel switch <team-slug> # Switch active team
vercel link# Link local dir to Vercel project
vercel project ls# List projects in current team
Memory Protocol (MANDATORY)
Before starting:
Read .claude/context/memory/learnings.md
After completing:
New pattern -> .claude/context/memory/learnings.md
Issue found -> .claude/context/memory/issues.md
Decision made -> .claude/context/memory/decisions.md
