bootstrap

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

Updated Aug 21, 2025
One-click install
npx skills add https://github.com/Adithiya-S/AI-Study-Companion --skill bootstrap-adithiya-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bootstrap
Source: https://github.com/Adithiya-S/AI-Study-Companion/tree/main/.agents/skills/bootstrap
Command: npx skills add https://github.com/Adithiya-S/AI-Study-Companion --skill bootstrap-adithiya-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a repository that depends on Vercel-linked resources often fails because developers run 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 via vercel link, provisions Postgres through the Neon integration, and pulls env vars before any database or dev command runs. - Secret-Safe Env Management: Generates AUTH_SECRET without printing it, stores it in Vercel, and verifies required env keys by comparing names only, never values. - Framework-Aware Setup: Handles Next.js + shadcn UI baselines and next-forge monorepos with per-app env files and pnpm migrate instead of db:push. - Use Case: You clone a Next.js repo backed by Neon Postgres and Clerk auth. The Skill links the Vercel project, adds the Neon integration, pulls .env.local, verifies all required keys, then runs db:push, db:seed, and dev in order. ## 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 Neon Postgres database?

Link the repo with vercel link, then run vercel integration add neon to provision Postgres through the Vercel-managed integration. Finish with vercel env pull to sync the connection variables into your local .env.local file.

How do I pull environment variables from Vercel to my local machine?

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

Why should I run vercel link before database migrations?

Running db:push or db:seed before linking fails because the database connection strings only exist after the project is linked and env vars are pulled. The bootstrap order ensures linkage and env verification complete before any migration runs.

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

Generate the secret with Node's crypto module into a shell variable, pipe it directly to vercel env add, then unset the variable. This stores the value in Vercel without ever printing it to logs or terminal output.

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 directories. They use per-app env files and pnpm migrate instead of db:push, and deploy as three separate Vercel projects.

What happens if required environment keys are missing after env pull?

The verification step diffs required key names from the env template against .env.local and stops if any are missing. You add the missing keys in Vercel and re-run vercel env pull before proceeding.