scaffold-projectlisted

# scaffold-project Take a **greenfield** project from empty to a stack that boots end-to-end: backend reachable on its framework-metadata endpoint, frontend reachable on its default page, every Dockerfile builds, `docker compose up` brings the whole topology up, a Playwright smoke spec drives the served frontend, and the design system locked upstream by `/deep-dive-feature` (its `docs/design-system/tokens.md`) is seeded into the frontend as CSS custom properties. Each surface commits as it lands, and the run ends by pushing the branch and opening a PR. No feature endpoints, no routes, no migrations, no auth knobs, no contract-derived paths. Those land later, when a feature task brings them in via the engineer lane. ## When to activate Activate when: - The user types `/scaffold-project`, or phrases like 'scaffold the project', 'bootstrap the worktree', 'set up the project skeleton', 'make compose bring everything up', 'kickoff the project skeleton'. Do NOT activate when: - The project already has any scaffolded surface (`backend/`, `frontend/`, `compose.yaml` / `docker-compose.yaml`, or `e2e/`) — this skill is **greenfield only**. Surface the gap and STOP; structural additions to an already-bootable project belong to the engineer lane. - `docs/architecture-decision-record/` is empty or doesn't declare a stack choice and a compose topology — scaffold MUST NOT guess at frameworks or services. Surface the gap and STOP. - The work the user wants is feature work — adding a h