← ClaudeAtlas

getting-startedlisted

Use when someone new to coding (or to AI-assisted coding) needs their machine set up — they say "set me up", "onboard me", "I just installed Claude Code", ask how to start coding with Claude, or want an existing setup checked or brought up to date (toolchain, editor, Docker, GitHub, Claude config). Idempotent and safe to re-run. macOS, Linux, and WSL2.
mickzijdel/dev-hooks · ★ 0 · Code & Development · score 71
Install: claude install-skill mickzijdel/dev-hooks
# getting-started Get someone from a fresh machine to "I can build and ship something with Claude Code." It meets people **wherever they are** — from someone who's never opened a terminal to an experienced developer who's just new to AI-assisted coding — by **asking their experience level once** (Step 2) and calibrating from there. The bar is not just "tools installed" but "they understand what just happened, at the depth that's right for them, and won't get their agent into trouble." Three 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. - **Teach as you go, at the right level.** Until Step 2 establishes the user's experience level, default to plain words and assume little prior knowledge; after it, match the explanation and technical depth to the rung they chose (the per-rung guidance lives in [`references/explanation-levels.md`](references/explanation-