new-projectlisted

# new-project — scaffold the house methodology Set the project up so the documentation-first pipeline (BLOG → RFC ↔ DRP → ARCHITECTURE/CR → WORK PLAN → reviews) is ready — and **self-contained**: the project gets its own copy of the templates and design system, so it no longer depends on the ONBOARDING repo's location. ## Target directory - **Default: the current working directory** (the project). Scaffold there. - If the user passes a path (`/new-project <path>`), scaffold into that path instead. - Confirm the **project name** (default: the directory name) and a one-line description. ## Locate ONBOARDING (source of the kit) Find the ONBOARDING repo to copy from — usually a sibling dir `../ONBOARDING`, or the repo this skill was installed from; ask the user if it isn't obvious. You need `ONBOARDING/templates/`, `ONBOARDING/assets/house.css`, and (for app UIs) `ONBOARDING/frontend-kit/`. ## Steps (copy in — don't symlink; the project must be standalone) 1. Create `docs/` and `docs/assets/`. 2. **Copy the design system:** `ONBOARDING/assets/house.css` → `docs/assets/house.css`. 3. **Copy the templates:** `ONBOARDING/templates/*` → `docs/templates/`. (So authoring works with no dependency on the ONBOARDING repo. A template links `../assets/house.css`, which from `docs/templates/` correctly resolves to `docs/assets/house.css`.) 4. **Seed the running docs** from the copied templates, filling project name/date: - `docs/DOCS_INDEX.md` ← `docs/templates/DOCS_INDEX.templa