backend-onboardlisted

# backend-onboard The single entry point for pointing the toolkit at a directory. Its job is to produce the two contract files the rest of the toolkit depends on — `ARCHITECTURE.md` and `MODULE_REGISTRY.md` — accurately reflecting *this* project, then route the user into the normal plan → build → test flow. It does **not** re-implement bootstrapping, planning, building, or testing — those are owned by `express-ts-bootstrap`, `backend-feature-planner`, `backend-module-builder`, and `backend-test-writer`. This skill establishes the contract and delegates; that keeps the whole suite DRY instead of duplicating four skills into one. ## Step 0 — Locate the project, then new-or-existing? First resolve **where the backend code lives** — the *project dir* — because everything below reads and writes relative to it, while `.claude/` stays at the repo root. See `../LAYOUT.md`. - The project dir is the repo root if code sits at the root, or a subfolder (e.g. `backend-<name>/` like `backend-shoply/`, or a plain `backend/`) if the user already keeps it there. Detect by where `package.json` / `src` actually are; if ambiguous (e.g. multiple candidate folders), ask which folder to onboard. - **Onboard is non-destructive: it never moves code.** It records the project *where it already is*. If the user wants existing root-level code relocated into `backend/`, that's a separate, explicit restructure — out of scope here. Then, inspecting that project dir: - **Empty, or no source code*