bootstrap

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a repository that depends on Vercel-linked resources often fails when 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: Runs preflight checks (Vercel CLI auth, project linkage), then env setup, then database and dev commands only after verification passes. - Postgres Provisioning Paths: Prefers Vercel-managed Neon integration, with dashboard and Neon CLI fallbacks when the managed flow 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 with a .env.example and Drizzle schema. The Skill links the Vercel project, adds the Neon integration, pulls env vars, verifies keys, then runs db:push, db:seed, and dev in order. ## Quick Start Ask the AI to bootstrap this repository by linking it to my Vercel project, pulling the environment variables, and running the database setup and 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 Neon Postgres database?

Link the repo with vercel link, then run vercel integration add neon to provision a managed Neon database. Finish with vercel env pull .env.local to sync the connection variables locally before running any database commands.

How to pull environment variables from Vercel to local development?

Run vercel env pull .env.local --yes after linking your project with vercel link. This downloads all environment variables from the Vercel project into a local file without printing secret values to the terminal.

Why should I not run db:push or dev before vercel env pull?

Database and dev commands fail when required environment variables like DATABASE_URL are missing locally. The bootstrap order gates migrations and dev server startup until project linking and env key verification are complete.

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

Yes, the Neon CLI is a supported fallback when Vercel-managed provisioning is unavailable. After creating resources with the Neon CLI, add the required env vars in Vercel and run vercel env pull again.

How do I generate AUTH_SECRET without exposing it in logs?

Generate it with node crypto randomBytes, pipe it directly into vercel env add without echoing, then unset the shell variable. The value is stored in Vercel and synced via vercel env pull, never appearing in terminal output.

How is bootstrapping different for next-forge monorepo projects?

next-forge projects use per-app env files and require pnpm migrate instead of db:push, which runs prisma format, generate, and db push. They deploy as three separate Vercel projects rooted at apps/app, apps/api, and apps/web.