dr-initlisted

# Initialize Darkroom Project Create a new project using a Darkroom starter. Darkroom maintains two: | Starter | Stack | When to use | |---|---|---| | **satus** | Next.js 16 + App Router + RSC + React 19 | Content-driven sites, SEO-critical, Vercel-friendly, projects that benefit from Server Components / Server Actions | | **novus** | React Router 7 + Vite + React 19 | SPA-leaning apps, projects that prefer the loader/action data model, projects without need for RSC, projects deploying to non-Vercel infra | ## Step 1 — Pick the starter If the user already specified ("/dr-init satus", "/dr-init novus", "create new react-router project"), use that. Otherwise ask: ``` Which starter? - satus (Next.js) — App Router, Server Components, Vercel-optimized - novus (React Router) — RR7, Vite, classic loader/action model ``` When the user is unsure, prefer **satus** for marketing/content sites and **novus** for app-heavy SPAs. ## Step 2 — Clone ### satus (Next.js) ```bash bunx degit darkroomengineering/satus $ARGUMENTS cd $ARGUMENTS bun install ``` ### novus (React Router) ```bash bunx degit darkroomengineering/novus $ARGUMENTS cd $ARGUMENTS bun install ``` ## Step 3 — Post-setup Both starters: 1. **Update package.json** — change `name`, `description`. 2. **Configure environment** — copy `.env.example` to `.env` (or `.env.local` for satus). 3. **Start dev** — `bun dev`. 4. **Open debug** — `Cmd/Ctrl + O` (satus) or `Cmd + .` / `Ctrl + O` (novus). ## What each starter includ