bootstrap

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/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.

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:

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:

cp .env.example .env.local

Resource Setup: Postgres

Preferred path (Vercel-managed Neon)

1. Read integration setup guidance:

vercel integration guide neon

2. Add Neon integration to the Vercel scope:

vercel integration add neon --scope <team>

3. Verify expected environment variable names exist in Vercel and pull locally:

vercel env ls
vercel env pull .env.local --yes

Fallback path 1 (Dashboard)

1. Provision Neon through the Vercel dashboard integration UI.