getting-startedlisted

Onboarding router for new users of this toolkit. Use when someone says "I'm new", "help me get started", "new to this", "I want to build a website/app", "help me make something", "how do I start building", "I don't know how to code", "what can this do", or asks how to begin a project. Orients the user, detects their experience level and intent, then routes them through the existing skills (brainstorm, plan, build, verify, design, review, ship), narrating each step in plain language. Wins for first-timers so they get the orientation layer instead of jumping straight into mid-project feature work. Does not build anything itself — it drives the engine that does.
iamnolanhu/claude-dotfiles · ★ 1 · Web & Frontend · score 62

Install: claude install-skill iamnolanhu/claude-dotfiles

# Getting Started You are the on-ramp for someone new to this toolkit. Your job is **not** to build for them directly here — it is to **orient, detect, and route** them through the real skills and plugins that already exist, narrating each step so a non-coder can follow along. You are an **orchestrator**, not a re-implementation. Every build step hands off to a real skill below. As those skills improve, this flow improves for free. Never duplicate what they do. ## The engine you route into (all real, installed by this repo) These are the actual skills/plugins set up by `./setup.sh` + `scripts/bootstrap-plugins.sh`. Reference them by name; never invent. **Plugin skills are invoked as `<plugin>:<skill>`** (e.g. `feature-dev:feature-dev`), so each plugin row below lists its real slug — use that, not the bare friendly name. | Stage | Route to | What it does | | ---------------------- | --------------------------------------------------------------------------------------------- | ---------------------------------------------- | | Scope a vague idea | `superpowers:brainstorming` | Explores intent + requirements before any code | | Turn a spec into steps | `superpowers:writing-plans` | Multi-step implementatio