name: vercel-deploy description: "Use during Stage 11 of the website factory pipeline to deploy the built client website to Vercel production via the Vercel CLI. Verifies the local build passes, runs vercel --prod --yes from the client website folder, captures the production URL, smoke-checks it returns 200, and writes vercel-url.txt + deploy-log.json. Halts before deploy if QA gates 10.4a or 10.4b are not complete (or explicitly overridden). Disabled from auto-invocation: deploy is always user-driven via /stage11 or /build-all." allowed-tools:

• Bash
• Read
• Write

disable-model-invocation: true metadata: version: "1.0.0"

Vercel Deploy Skill

Deploy the built client website from clients/[Client Name]/[Client Name] Website/ to a Vercel project using the Vercel CLI.

Pre-requisites

• Vercel CLI installed globally: npm i -g vercel
• User is logged in: vercel login (one-time setup, persists)
• The Vite build completes without errors: npm run build

Execution steps

Step 1, Navigate to the build folder

cd "clients/[Client Name]/[Client Name] Website"

Step 2, Run the production build

npm run build

Confirm dist/ folder exists and is non-empty. If the build fails, halt and report the error.

Step 3, Link the project (first-time only)

If no .vercel/ folder exists in the build directory, link it:

vercel link

Follow the prompts:

• Set up and deploy: Yes
• Which scope: pick the correct Vercel org/account
• Link to existing project? No (first time)
• Project name: [client-slug]-website
• Directory: . (current folder)
• Override settings: No

This creates .vercel/project.json. On subsequent deploys, this file handles the link automatically.

Step 4, Deploy to production

vercel --prod

Capture the production URL from the output (format: https://[client-slug]-website.vercel.app or the custom domain if already configured).

Step 5, Verify deployment

curl -s -o /dev/null -w "%{http_code}" https://[deployed-url]

Expect 200. If not 200, check Vercel dashboard for build/deployment errors.

Step 6, Save the URL

Write the production URL to:

clients/[Client Name]/Pipeline Data/deploy/vercel-url.txt

This file is read by the proposal agent at Stage 13 for the iframe preview.

Step 7, Optional: custom domain setup

Custom domain configuration is done in the Vercel dashboard, not via CLI. After deploy:

1. Vercel dashboard > Project > Settings > Domains
2. Add [client-domain].com and www.[client-domain].com
3. Update DNS at client's registrar:

• A record: 76.76.21.21 (Vercel IP)
• CNAME www: cname.vercel-dns.com

1. Vercel auto-provisions SSL once DNS propagates (usually under 5 minutes)

Update an existing deployment

Re-run npm run build && vercel --prod from the build folder. The existing .vercel/project.json link handles everything else automatically.

What to do if vercel link fails

1. Delete .vercel/ folder and retry
2. Check vercel whoami to confirm you're logged in as the right account
3. If project already exists on Vercel, use "Link to existing project: Yes" and enter the

project name

Failure handling