ccc-onboardlisted

# /ccc-onboard — New Contributor Onboarding **CC Commander** · /ccc-onboard · Role → first task → first hour Use this when a contributor is new to the repository and needs a practical first hour, not a generic tour. Build the guide from the repo’s own instructions and scripts. ## Response Shape Always return these sections: 1. Brand header: ```markdown **CC Commander** · /ccc-onboard · Contributor first hour ``` 2. Repo context: Read only the files that exist: - `CLAUDE.md` for local conventions, required tools, test commands, and workflow rules - `BIBLE.md` for product architecture, domain language, and non-negotiable project rules - `package.json` for scripts, package manager clues, and workspace structure - `README.md` only if the first three do not provide enough starter links Summarize: ```markdown Repo: <name> · package manager: <npm|bun|pnpm|yarn|unknown> · scripts: <top useful scripts> · primary stack: <detected stack> ``` 3. Role picker — `AskUserQuestion` Never show more than four options in one picker. The first picker covers the three most common code roles plus a "More roles" option; the second picker covers docs and first-PR onboarding. ```yaml question: "What kind of contributor are you onboarding?" header: "CC Commander Onboard" multiSelect: false autocomplete: true options: - label: "Frontend" value: "frontend" description: "UI, components, client flows, accessibility, and visual polish." preview: "First task focuses on finding a s