nextjs-app

1# nextjs-app
2 
3Bootstrap a new Next.js web app the way this owner builds them: App Router,
4TypeScript strict, current stable packages, no deprecated APIs, a clean feature
5structure, and the house git and CI workflow.
6 
7First read these shared rules (they override anything you remember):
8`../shared/house-rules.md`, `../shared/no-ai-attribution.md`,
9`../shared/git-and-ci.md`, `../shared/docs-and-context.md`,
10`../shared/hardening.md`, and (for public repos) `../shared/open-source-docs.md`.
11 
12## Step 0. Get the brief, then ask the variant questions (hard stop)
13 
14This is a hard stop. Do not run any scaffolding command until the user has
15answered.
16 
17First, get the project brief: one paragraph on what the app does, its main
18features, target users, and any hard constraints. If the user has not given one,
19ask for it. The brief drives naming, the route groups, and the data model.
20 
21Then present the variant choices below, wait for the answers, and build. If a
22choice has multiple options, ask; do not assume. Ask in one batch.
23 
241. Repo visibility: private, open-source (public), or private-plus-open-source
25   (a private product with a separate public core or SDK). See
26   `references/variants.md`.
272. Data layer: Prisma + Postgres (default), a different DB, or none yet.
283. Auth: next-auth v5 (default), Clerk, or none yet.
294. UI kit: shadcn/ui + Tailwind (default), Mantine, or plain Tailwind.
305. Deploy target: Vercel (default) or self-host (Docker).
316. Package manager: pnpm (default) or npm.
32…