bootstrap

Execute bootstrap in strict order. Do not run migrations or development server until project linking and environment verification are complete.

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

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

Generate a high-entropy secret without printing it, then store it in Vercel and refresh local env:

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

Compare required keys from template file against .env.local keys (names only, never values):

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.

After linkage + env verification:

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.

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.

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.

Return a final bootstrap summary in this format:

## Bootstrap Result
- **Linked Project**: <team>/<project>
- **Resource Path**: 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

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

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.