bootstrap
/bootstrap
Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order.
- Author
- vercel-labs ↗
- Repository
- vercel-plugin ↗
- Licence
- Apache-2.0
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order.
Original author description
Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order.
How it works
- Rules
- Preflight
- Resource Setup: Postgres
- AUTHSECRET Generation
- Env Verification
- App Setup
- UI Baseline for Next.js + shadcn Projects
- Bootstrap Verification
- Summary Format
- Bootstrap Next Steps
SKILL.md preview
---
name: bootstrap
description: Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order.
metadata:
priority: 8
docs:
- "https://vercel.com/docs/getting-started-with-vercel"
- "https://nextjs.org/docs/app/getting-started/installation"
sitemap: "https://vercel.com/sitemap.xml"
pathPatterns:
- '.env.example'
- '.env.sample'
- '.env.template'
- 'README*'
- 'docs/**/setup*'
- 'package.json'
- 'drizzle.config.*'
- 'prisma/schema.prisma'
- 'auth.*'
- 'src/**/auth.*'
bashPatterns:
- '\\bcp\\s+\\.env\\.(?:example|sample|template)\\s+\\.env\\.local\\b'
- '\\b(?:npm|pnpm|bun|yarn)\\s+run\\s+db:(?:push|seed|migrate|generate)\\b'
- '\\b(?:npm|pnpm|bun|yarn)\\s+run\\s+dev\\b'
- '\\bvercel\\s+link\\b'
- '\\bvercel\\s+integration\\s+(?:add|install)\\b'
- '\\bvercel\\s+env\\s+pull\\b'
importPatterns:
- '@neondatabase/serverless'
- 'drizzle-orm'
- '@upstash/redis'
- '@vercel/blob'
- '@vercel/edge-config'
- '@vercel/global-config'
- 'next-auth'
- '@auth/core'
- 'better-auth'
chainTo:
-
pattern: '@vercel/(postgres|kv)|\b(KV_REST_API_URL|POSTGRES_URL)\b'
targetSkill: vercel-storage
message: '@vercel/postgres and @vercel/kv are sunset — loading Vercel Storage guidance for Neon and Upstash migration.'
-
pattern: 'from\s+[''""](next-auth|@auth/core|@clerk/nextjs|better-auth)[''""]'
targetSkill: auth
message: 'Auth library detected during bootstrap — loading Auth guidance for Clerk Marketplace setup and middleware patterns.'
-
pattern: 'OPENAI_API_KEY|ANTHROPIC_API_KEY|AI_GATEWAY'
targetSkill: env-vars
message: 'AI provider env vars detected — loading Environment Variables guidance for OIDC-based auth via vercel env pull.'
skipIfFileContains: 'VERCEL_OIDC|vercel env pull'
retrieval:
aliases:
- project setup
- repo init
- getting started
- scaffold
intents:
- set up project
- initialize repo
- link vercel project
- pull env vars
entities:
- vercel link
- env pull
- database setup
- first run
---
# Project Bootstrap Orchestrator
Execute bootstrap in strict order. Do not run migrations or development server until project linking and environment verification are complete.
## Rules
- Do not run `db:push`, `db:migrate`, `db:seed`, or `dev` until Vercel linking is complete and env keys are verified.
- Prefer Vercel-managed provisioning (`vercel integration ...`) for shared resources.
- Use provider CLIs only as fallback when Vercel integration flow is unavailable.
- Never echo secret values in terminal output, logs, or summaries.
## Preflight
1. Confirm Vercel CLI is installed and authenticated.
```bash
vercel --version
vercel whoami
```
2. Confirm repo linkage by checking `.vercel/project.json`.
3. If not linked, inspect available teams/projects before asking the user to choose:
```bash
vercel teams ls
vercel projects ls --scope <team>
vercel link --yes --scope <team> --project <project>
```
4. Find the env template in priority order: `.env.example`, `.env.sample`, `.env.template`.
5. Create local env file if missing:
```bash
cp .env.example .env.local
```
## Resource Setup: Postgres
### Prisma ORM projects
If the repo has `prisma/schema.prisma`, provision Prisma Postgres with these steps instead of the preferred path below:
```bash
vercel integration guide prisma
vercel integration add prisma --scope <team>
```
It sets `DATABASE_URL` to the direct connection string. Then verify and pull env vars as in step 3 of the preferred path below. For production traffic from Vercel Functions, add the pooled string as described in the `vercel-storage` skill.
### Preferred path (Vercel-managed Neon)
1. Read integration setup guidance:
```bash
vercel integration guide neon
```
2. Add Neon integration to the Vercel scope:
```bash
vercel integration add neon --scope <team>
```
3. Verify expected environment variable names exist in Vercel and pull locally:
```bash
vercel env ls
vercel env pull .env.local --yes
```
### Fallback path 1 (Dashboard)
1. Provision Neon through the Vercel dashboard integration UI.
2. Re-run `vercel env pull .env.local --yes`.
### Fallback path 2 (Neon CLI)
Use Neon CLI only when Vercel-managed provisioning is unavailable. After creating resources, add required env vars in Vercel and pull again.
## AUTH_SECRET Generation
Generate a high-entropy secret without printing it, then store it in Vercel and refresh local env:
```bash
AUTH_SECRET="$(node -e "console.log(require('node:crypto').randomBytes(32).toString('base64url'))")"
printf "%s" "$AUTH_SECRET" | vercel env add AUTH_SECRET production,preview
printf "%s" "$AUTH_SECRET" | vercel env add AUTH_SECRET development # separate command: development-only adds default to Config
unset AUTH_SECRET
vercel env pull .env.local --yes
```
## Env Verification
Compare required keys from template file against `.env.local` keys (names only, never values):
```bash
template_file=""
for candidate in .env.example .env.sample .env.template; do
if [ -f "$candidate" ]; then
template_file="$candidate"
break
fi
done
comm -23 \
<(grep -E '^[A-Za-z_][A-Za-z0-9_]*=' "$template_file" | cut -d '=' -f 1 | sort -u) \
<(grep -E '^[A-Za-z_][A-Za-z0-9_]*=' .env.local | cut -d '=' -f 1 | sort -u)
```
Proceed only when missing key list is empty.
## App Setup
After linkage + env verification:
```bash
npm run db:push
npm run db:seed
npm run dev
```
Use the repository package manager (`npm`, `pnpm`, `bun`, or `yarn`) and run only scripts that exist in `package.json`.
## UI Baseline for Next.js + shadcn Projects
After linkage and env verification, establish the UI foundation before feature work:
1. Add a baseline primitive set: `npx shadcn@latest add button card input label textarea select switch tabs dialog alert-dialog sheet dropdown-menu badge separator skeleton table`
2. Apply the Geist font fix in `layout.tsx` and `globals.css`.
3. Confirm the app shell uses `bg-background text-foreground`.
4. Default to dark mode for product, admin, and AI apps unless the repo is clearly marketing-first.
## Bootstrap Verification
Confirm each checkpoint:
- `vercel whoami` succeeds.
- `.vercel/project.json` exists and matches chosen project.
- Postgres integration path completed (Vercel integration, dashboard, or provider CLI fallback).
- `vercel env pull .env.local --yes` succeeds.
- Required env key diff is empty.
- Database command status is recorded (`db:push`, `db:seed`, `db:migrate`, `db:generate` as applicable).
- `dev` command starts without immediate config/auth/env failure.
If verification fails, stop and report exact failing step plus remediation.
## Summary Format
Return a final bootstrap summary in this format:
```md
## Bootstrap Result
- **Linked Project**: <team>/<project>
- **Resource Path**: vercel-integration-prisma | vercel-integration-neon | dashboard-neon | neon-cli
- **Env Keys**: <count> required, <count> present, <count> missing
- **Secrets**: AUTH_SECRET set in Vercel (value never shown)
- **Migration Status**: not-run | success | failed (<step>)
- **Dev Result**: not-run | started | failed
```
## Bootstrap Next Steps
- If env keys are still missing, add the missing keys in Vercel and re-run `vercel env pull .env.local --yes`.
- If DB commands fail, fix connectivity/schema issues and re-run only the failed db step.
- If `dev` fails, resolve runtime errors, then restart with your package manager's `run dev`.
## next-forge Projects
If the project was scaffolded with `npx next-forge init` (detected by `packages/auth` + `packages/database` + `@repo/*` imports; package manager is chosen at init):
1. Env files are per-app (`apps/app/.env.local`, `apps/web/.env.local`, `apps/api/.env.local`) plus `packages/database/.env`.
2. Run the `migrate` script with the repo's package manager (not `db:push`) — it runs `prisma format` + `prisma generate` + `prisma migrate dev` and prompts for a migration name.
3. Minimum env vars: `DATABASE_URL`, `NEXT_PUBLIC_APP_URL`, `NEXT_PUBLIC_WEB_URL`, `NEXT_PUBLIC_API_URL` (URLs are pre-configured for local dev).
4. Optional services (Clerk, Stripe, Resend, PostHog, etc.) can be skipped initially — integrations whose keys are unset are skipped at runtime. Delete the empty `KEY=""` placeholders copied from `.env.example`: an empty string fails the `keys.ts` format checks.
5. Deploy as 3 separate Vercel projects with root directories `apps/app`, `apps/api`, `apps/web`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · vercel-labs/vercel-plugin | 100 | Apache-2.0 |
| renzrollon/interlock | 100 | MIT |
| bytedance/deer-flow | 100 | MIT |
| Nazhra05/Super-set | 100 | MIT |
| Nazhra05/Super-set | 100 | MIT |
| chaordic-io/discipline | 100 | MIT |
| geekatron/jerry | 100 | Apache-2.0 |
| fullymiddleaged/clawness | 100 | MIT |
| vercel/vercel-plugin | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 10b07cf74911 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100local-bootstrap-188c0d6a
Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order. - 95vercel-cli
Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, managing domains, or interacting with the Vercel platform from the command line. - 100vercel-cli
Deploy apps to Vercel. Use when asked to deploy, ship, or publish a web application, or manage Vercel projects, domains, and environment variables. - 100deploy-to-vercel
Use when deploying to Vercel - linking the project, env vars per environment and vercel env pull, protected previews, the config file, regions near the database, crons, rolling releases and rollback, the firewall, and gated prebuilt deploys from CI. - 100vercel-deployment
Deploy Next.js applications to Vercel with proper configuration. Use when setting up deployment, configuring environment variables, edge functions, or troubleshooting builds. Activates for deployment issues, environment setup, and Vercel configuration. - 100vercel-multi-env-setup
Configure Vercel across development, preview, and production environments with scoped secrets. Use when setting up per-environment configuration, managing environment-specific variables, or implementing environment isolation on Vercel. Trigger with phrases like "vercel…