bootstrap

Orchestrates Vercel project linking, environment provisioning, and first-run database setup for repositories.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill bootstrap-aarnavbaddam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bootstrap
Source: https://github.com/AarnavBaddam/skills/tree/main/bootstrap
Command: npx skills add https://github.com/AarnavBaddam/skills --skill bootstrap-aarnavbaddam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a repository that depends on Vercel-linked resources (Postgres, auth, managed integrations) involves many ordered steps—linking the project, provisioning integrations, pulling environment variables, and running database commands—and running them in the wrong order causes confusing failures. This Skill enforces the correct safe sequence so bootstrapping succeeds on the first attempt. ## Core Features & Use Cases - Ordered Bootstrap Workflow: Runs preflight checks (Vercel CLI auth, project linkage), resource provisioning, env verification, and only then executes db:push, db:seed, and dev commands. - Vercel-Managed Provisioning with Fallbacks: Prefers vercel integration add neon, with dashboard and Neon CLI fallback paths when managed provisioning is unavailable. - Secret-Safe Env Management: Generates AUTH_SECRET without printing it, stores it in Vercel, and verifies required env keys by name only—never exposing values. - Use Case: You clone a Next.js repo using Neon Postgres and Auth.js. The Skill links the repo to the correct Vercel project, provisions Neon, pulls env vars, verifies all required keys exist, then runs migrations and starts the dev server—reporting a structured bootstrap summary. ## Quick Start Bootstrap this repository by linking it to my Vercel project, provisioning the database, pulling environment variables, and starting the dev server.

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 Next.js project with Vercel Postgres and environment variables?

Link the repo with vercel link, provision Postgres via vercel integration add neon, then run vercel env pull to populate .env.local. Verify all keys from .env.example exist before running db:push and the dev server.

What order should I run vercel link, env pull, and database migrations?

Always link the project first, then provision integrations, then pull environment variables, and only after verifying required env keys run db:push, db:seed, or dev. Running migrations before env verification causes connection failures.

How do I generate and store AUTH_SECRET without exposing it?

Generate it with Node's crypto.randomBytes, pipe it directly into vercel env add without echoing, unset the shell variable, then re-run vercel env pull. The value is stored in Vercel and never printed to terminal output or logs.

Can I use Neon CLI instead of the Vercel integration for Postgres?

Yes, Neon CLI is a supported fallback when Vercel-managed provisioning is unavailable. After creating resources with the Neon CLI, manually add the required environment variables in Vercel and pull them locally again.

Why does my next-forge project fail env validation on startup?

next-forge uses per-app env files and optional services like Stripe or Resend whose missing keys fail validation. Remove unused @repo/* imports from each app's env.ts file, and run pnpm migrate instead of db:push.