What problem does it solve? Setting up a repository that depends on Vercel-linked resources often fails because developers run database migrations or dev servers before linking the project and pulling environment variables. This Skill enforces the correct bootstrap order so linking, env provisioning, and first-run commands happen safely. ## Core Features & Use Cases - Ordered Bootstrap Workflow: Verifies Vercel CLI authentication, links the project, provisions Postgres via the Neon integration, and pulls env vars before any db or dev command runs. - Secret-Safe Env Management: Generates AUTH_SECRET without printing it, stores it in Vercel, and diffs required env keys by name only, never exposing values. - Fallback Paths & Verification: Supports dashboard and Neon CLI fallbacks, next-forge monorepo conventions, and a checkpoint-based verification with a structured summary report. - Use Case: After cloning a Next.js repo with a .env.example and drizzle.config.ts, use this Skill to link the Vercel project, provision Neon Postgres, pull .env.local, and run db:push and dev only once env verification passes. ## Quick Start Set up this repository by linking it to my Vercel project, provisioning the database, pulling environment variables, and starting the dev server in the correct order.