Appearance
Prerequisites — the toolchain, verified before anything runs
CLAUDE.md cited this page for months before it existed (measured 2026-08-28). R-01 in Operating rules says: before any setup, build, test or deploy command, verify the toolchain is present at the right versions and install what is missing — never proceed with a step whose tool is absent.
The tools, and how to check each
| Tool | Version / source | Check | Install (Windows · macOS) |
|---|---|---|---|
| git + GitHub CLI | current | git --version · gh auth status | winget Git.Git, GitHub.cli · brew git gh |
| Node + npm | 22 (.nvmrc) | node -v prints v22.x | nvm-windows nvm use · nvm use |
| Deno | current | deno --version | winget DenoLand.Deno · brew deno |
| Supabase CLI | current | npx supabase --version; then npx supabase projects list and read the names — the stored login is volatile state | npm shim via the repo (npm run sb) |
| Docker Desktop | current; data folder on D: | docker info | installer; set the data location to D:\DevCache\DockerDesktop before first start (check:disk) |
| wrangler | apps/web devDependency (^4.124) | npx wrangler --version from apps/web | npm install |
| Playwright browsers | chromium | npx playwright install --with-deps chromium | same |
⚠ Never a local SonarQube container — it crashed Docker Desktop on the 16 GB box (QRS-252); CI's sonar job is the authority and the VS Code SonarLint extension the local substitute.
Development never touches C:
D:\WorkSpace\DevArea\<project> for code, D:\DevCache\* for caches; npm run check:disk asserts it (QRS-205). Full policy: Windows build environment § Disk hygiene.
Then
nvm use && npm install, then npm run type-check and npm test before relying on the checkout. The mobile and web apps each own their dev server; see the commands table in CLAUDE.md and Quality gates.