helplisted

Shows where you are in the Web Studio pipeline and what to do next; `commands` lists every command with its description, `guide [topic]` opens the playbook (what to run in every situation). Use when the user asks 'what now', 'what should I do next', 'which commands exist', 'what do I do if…', or is stuck.
gonimar/claude-web-studio · ★ 0 · Web & Frontend · score 78

Install: claude install-skill gonimar/claude-web-studio

# Help — what next? Read-only. Not a full audit (that is `/adopt`), a quick orientation. Reply in the project conversation language. ## Phase 0: Reference modes (`commands` · `guide`) Two arguments answer a reference question instead of "what next" and end without the closing `AskUserQuestion` — there is nothing to decide (rule 7). - **`commands`** — every command with its description. Source: the skills themselves, never memory — Glob `<plugin root>/skills/*/SKILL.md` (the "Plugin root:" line of the session-start context) and `.claude/skills/*/SKILL.md` (copy mode, and project-local skills); read `name:`, `description:` (first sentence) and `argument-hint:` from each frontmatter. Group by the catalog's phases in catalog order (a skill in no phase goes under "Maintenance and teams"), one line per command: `/name <argument-hint> — first sentence of the description`. Mark the catalog's required steps with `*`. Then one line: `Details: /help guide · .claude/docs/playbook.md · README of the plugin`. - **`guide [topic]`** — the playbook `.claude/docs/playbook.md` (seeded by `/init`/`/update`; fall back to `<plugin root>/docs/playbook.md`; a translation next to it in `.claude/docs/readme/PLAYBOOK.<lang>.md` when the project's conversation language has one — prefer it). Without a topic: print the playbook's table of contents (its `##` and `###` headings with numbers) and the line `/help guide <topic> prints one section`. With a topic: find the heading that matc