policyengine-vercel-deployment

Automate PolicyEngine frontend deployments to Vercel with team-scoped naming.

2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/PolicyEngine/policyengine-skills --skill policyengine-vercel-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: policyengine-vercel-deployment
Source: https://github.com/PolicyEngine/policyengine-skills/tree/main/skills/tools-and-apis/policyengine-vercel-deployment-skill
Command: npx skills add https://github.com/PolicyEngine/policyengine-skills --skill policyengine-vercel-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploys PolicyEngine frontend apps to Vercel with a standardized, team-scoped workflow, including naming conventions and environment handling.

Core Features & Use Cases

  • Team-scoped deployment: Links projects to the policy-engine team and applies the policyengine--{repo-name} naming pattern.
  • One-click first and subsequent deploys: Provides clear steps for initial deployment and subsequent releases.
  • Environment configuration and verification: Guidance on NEXT_PUBLIC_* variables and vercel.json configuration, with a quick verify step.

Quick Start

Link the project to the policy-engine scope and deploy with vercel --prod.

Frequently Asked Questions about policyengine-vercel-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Next.js frontend to Vercel under a specific team scope?

To deploy a Next.js frontend to Vercel under a team scope, link the project to the policy-engine team and apply the policyengine--{repo-name} naming pattern before running vercel --prod.

What naming convention should I use for Vercel project deployments?

Vercel project deployments should use the policyengine--{repo-name} naming convention to ensure proper team-scoped linking and standardized project identification across the organization.

How do I configure environment variables for a Next.js app on Vercel?

Configure Next.js environment variables on Vercel by setting NEXT_PUBLIC_* variables in your project settings or vercel.json to expose them to the browser during the build process.

Why is my production URL not accessible after a Vercel deployment?

If your production URL is not accessible after a Vercel deployment, verify the vercel.json configuration, check Next.js compatibility settings, and ensure the deployment finished successfully without build errors.

What is the difference between the first deploy and subsequent deploys to Vercel?

The first deploy to Vercel requires linking the project to the team scope and setting up environment variables, while subsequent deploys simply require running vercel --prod to push new releases.