bootstrap

Orchestrates Vercel project linking, environment provisioning, and first-run database setup in safe order.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/ridhijain709/AIPORSCHE --skill bootstrap-ridhijain709
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bootstrap
Source: https://github.com/ridhijain709/AIPORSCHE/tree/main/.agents/skills/bootstrap
Command: npx skills add https://github.com/ridhijain709/AIPORSCHE --skill bootstrap-ridhijain709

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about bootstrap

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

FAQPage Schema
How do I set up a Vercel project with a Postgres database from the CLI?

Authenticate with vercel whoami, link the repo with vercel link, then add the Neon integration using vercel integration add neon. Finally run vercel env pull .env.local to sync the database connection variables locally before running migrations.

How do I pull Vercel environment variables into a local env file?

Run vercel env pull .env.local --yes after the project is linked via vercel link. This writes all environment variables from the Vercel project into your local file, which you can verify against the keys listed in .env.example.

Why should I run vercel link before database migrations?

Database commands like db:push and db:seed require connection strings that only exist after the project is linked and env vars are pulled. Running migrations first fails because DATABASE_URL or POSTGRES_URL is missing from the local environment.

How do I generate an AUTH_SECRET without exposing it in terminal output?

Generate it with node crypto randomBytes, pipe it directly into vercel env add AUTH_SECRET for each environment, then unset the shell variable. This stores the secret in Vercel without printing the value to logs or terminal history.

Does this bootstrap flow work with next-forge monorepos?

Yes, next-forge projects are detected via pnpm-workspace.yaml and packages/auth plus packages/database. They use per-app env files, pnpm migrate instead of db:push, and deploy as three separate Vercel projects rooted at apps/app, apps/api, and apps/web.

What should I do when the Vercel Neon integration is unavailable?

Use the dashboard fallback by provisioning Neon through the Vercel integration UI, or use the Neon CLI directly as a second fallback. After either path, add the required env vars in Vercel and re-run vercel env pull.