← ClaudeAtlas

monorepo-structurelisted

Use at :stack — choosing between a next-monolith and a multi-service repository shape, with both shapes as measured in winning repositories.
rogerjeasy/win-hackathon · ★ 0 · AI & Automation · score 60
Install: claude install-skill rogerjeasy/win-hackathon
# Repository shape `:stack` picks one of two shapes, once, before anything else gets written. Both shapes below are measured directly from a winning repository's working tree, not sketched from what a Next.js monorepo "usually" looks like. ## next-monolith Kintwadi (Best Design) is one Next.js app. The marketing site, auth, and the entire authenticated product live inside a single `src/`, and the thing that would normally need its own deploy target is instead a route group. ``` $ ls src/app (app) about api blog contact e favicon.ico forgot-password globals.css hipaa how-it-works invite layout.tsx manifest.ts page.tsx pricing privacy reset-password security sign-in sign-up style-guide terms ``` `(app)` is a Next.js route group — the parenthesised segment is stripped from the URL, so everything inside it (`dashboard`, `people`, `medications`, `appointments`, `incidents`, `admin`, nineteen folders total) resolves to `/dashboard`, `/people`, and so on, while sharing the one `layout.tsx` that sits alongside them and gates every one of those folders on a session check. It sits as a sibling to `about`, `pricing`, and `sign-in` inside the *same* `src/app` — the public marketing shell and the protected product are one deploy artifact, distinguished only by which folder a route lives in. ``` $ ls src/db __tests__ admin-queries.ts demo-incident.ts invitations.ts rls.ts setup-notify.ts admin-db.ts audit.ts index.ts queries.ts sc