getting-startedlisted

# getting-started Get someone from a fresh machine to "I can build and ship something with Claude Code." Written for people **new to coding** — so the bar is not just "tools installed" but "they understand what just happened and won't get their agent into trouble." Two rules that shape everything below: - **Idempotent + upgrade-aware.** Re-running is always safe. Every step checks what's already there (via the audit script) and either installs what's missing or upgrades what's behind — never a blind re-install. mise does the heavy lifting: `mise install` reproduces, `mise upgrade` brings tools current. - **Detect, then confirm.** Install CLI tools as you go, but **stop and ask the user before** anything that needs `sudo`, installs a GUI app (VS Code, Docker), or changes their global Claude config. Explain what each thing is *for* in plain language as you go — link the reference docs rather than dumping walls of text. ## Platform macOS, Linux, and **WSL2** (all bash). If the audit reports `os=unknown` or the user is on **native Windows**, the first task is WSL2: have them run `wsl --install` in an admin PowerShell, reboot, then re-run this skill **inside the Ubuntu/WSL shell**. Docker Desktop and VS Code install on the Windows side and integrate with WSL automatically; everything else lives in WSL. Don't attempt a PowerShell-native install. ## Workflow ### 1. Audit ```bash bash "$CLAUDE_PLUGIN_ROOT/skills/getting-started/scripts/onboard_check.sh" ``` (`$CL