onboard-clientlisted

# Onboard Client Turns a signed WordPress deal into a fully set-up studio project. Orchestrates existing skills in sequence; where no automation exists yet (Harvest, Chrome bookmarks, remote git repo), it stops and tells Mark exactly what to do by hand rather than guessing or attempting something fragile. **The sequence:** Quiz → Commission (Asana + registry) → Tech access request → DDEV codebase → Dropbox folder → Manual-steps checklist. Tech access goes out early, right after commissioning — the default project type ("existing site") can't be pulled into DDEV until the client responds with credentials, so there's no point blocking the rest of the workflow on it. If this ordering is wrong for a given project, say so and skip ahead. --- ## Step 1 — Quiz Ask Mark for (don't guess): - **Client name** — for the Dropbox folder, Asana project, and tech access greeting. Use `$ARGUMENTS` if given, otherwise ask. - **Contact name** — who the tech access request is addressed to (may differ from the client/company name). - **Project name** — short descriptive name for Asana/CLAUDE.md (e.g. "Andrew Techstyle Rebuild"). - **Prefix** — 2–5 uppercase chars for Asana task IDs (e.g. `TSTY`). Suggest one from the client name if not given. - **Project type** — this branches Steps 3–4: - **Existing site** (default, most common) — Mark inherits a live WordPress site. DDEV gets set up as an empty shell; pulling the actual site content is a manual step once tech access arr