nextjs-app

Bootstrap a new Next.js web app the way this owner builds them: App Router, TypeScript strict, current stable packages, no deprecated APIs, a clean feature structure, and the house git and CI workflow.

First read these shared rules (they override anything you remember): ../shared/house-rules.md, ../shared/no-ai-attribution.md, ../shared/git-and-ci.md, ../shared/docs-and-context.md, ../shared/hardening.md, and (for public repos) ../shared/open-source-docs.md.

Step 0. Get the brief, then ask the variant questions (hard stop)

This is a hard stop. Do not run any scaffolding command until the user has answered.

First, get the project brief: one paragraph on what the app does, its main features, target users, and any hard constraints. If the user has not given one, ask for it. The brief drives naming, the route groups, and the data model.

Then present the variant choices below, wait for the answers, and build. If a choice has multiple options, ask; do not assume. Ask in one batch.

1. Repo visibility: private, open-source (public), or private-plus-open-source (a private product with a separate public core or SDK). See references/variants.md.
2. Data layer: Prisma + Postgres (default), a different DB, or none yet.
3. Auth: next-auth v5 (default), Clerk, or none yet.
4. UI kit: shadcn/ui + Tailwind (default), Mantine, or plain Tailwind.
5. Deploy target: Vercel (default) or self-host (Docker).
6. Package manager: pnpm (default) or npm.

If the user already answered some of these in their prompt, do not re-ask.

Step 1. Verify environment and current versions