vercel_skill

Overview

This skill deploys and configures applications on Vercel, with focused support for Next.js, serverless functions, edge functions, Vercel KV, and Postgres. It helps set up vercel.json, manage environment variables, schedule cron jobs, and optimize deployments for the edge network. Use it to automate deployments, tune function settings, and integrate Vercel platform features into your app lifecycle.

How this skill works

The skill generates or validates vercel.json configuration, prepares build and output settings, and scripts CLI commands for deploy and production deploy. It scaffold serverless and edge function handlers, Next.js App Router endpoints, and examples for ISR, Vercel KV, and Postgres usage. It also provides commands for managing env vars, cron schedules, and regional/function resource settings to match performance and cost goals.

When to use it

• Deploy a Next.js app to Vercel or push a production release.
• Create or tune serverless functions and edge runtimes for low-latency APIs.
• Configure vercel.json for builds, rewrites, headers, and regions.
• Set up Vercel KV or Postgres access patterns and examples.
• Manage environment variables and secrets for local and production workflows.
• Schedule recurring jobs using Vercel Cron endpoints.

Best practices

• Specify buildCommand, outputDirectory, and framework in vercel.json to ensure consistent builds.
• Pin function memory and maxDuration for predictable costs and behavior.
• Prefer edge runtime for low-latency public APIs and serverless for heavier server logic.
• Use environment secrets (vercel env add) and vercel env pull for local development .env files.
• Add HTTP headers and CORS rules in vercel.json for API endpoints to avoid runtime surprises.
• Use ISR revalidate for pages that need frequent but bounded freshness instead of rebuilding every request.

Example use cases

• Quickly deploy a Next.js site: configure vercel.json, run vercel, then vercel --prod for production.
• Create an edge API endpoint returning JSON for geo-distributed low-latency responses.
• Implement a serverless API that queries Vercel Postgres and returns data from a handler in api/*.ts.
• Store session metadata and counters in Vercel KV with set/get/incr examples for fast state.
• Schedule a nightly cleanup or report using a Vercel cron path that validates a secret header.