Initialize Darkroom Project

Create a new project using a Darkroom starter. Darkroom maintains two:

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

bunx degit darkroomengineering/<satus|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).

Project structure

satus

app/                 # Next.js routes
components/          # React components
lib/
├── hooks/          # Custom hooks
├── integrations/   # Third-party clients
├── styles/         # Global CSS, Tailwind
└── utils/          # Pure utilities

novus

app/
├── root.tsx        # Root layout
├── routes/         # Route modules (file-based)
└── routes.ts       # Optional explicit route config
components/         # React components
hooks/              # Custom hooks
integrations/       # Third-party clients
styles/             # Global CSS, Tailwind
utils/              # Pure utilities

Don't use

• create-next-app / create-react-app — missing Darkroom standards
• Manual setup — too many things to configure

Output

After initialization:

• Confirm project created and which starter was used
• List the next steps (env, dev server)
• Offer to start the dev server