component-builderlisted

# Component Builder Turn a plain-English request ("I want a skill that does X and Y") into a correct, ready-to-use Claude Code component. The user usually knows what they want but not how to write the front matter — your job is to articulate it well. ## When to use The user asks to build / create / scaffold an **agent**, **skill**, or **slash command**. If they describe a recurring job, a specialist reviewer, or a "/command", this applies. ## Step 1 — Settle the spec Infer from the request; only ask if genuinely ambiguous. - **type** — agent (clean-context specialist, parallelizable, own model), skill (procedure invoked in the main session), or command (a `/slash` prompt). - **name** — Title Case; it becomes a kebab-case slug for the filename and front-matter `name`. - **description** — *this is the trigger.* Be specific about **WHEN** to use it so it auto-invokes without misfiring. For agents that should fire often, start with **"Use proactively when…"**. Keep it tight (≈15–300 chars) — front matter is read on every turn (progressive disclosure), so don't bloat it. - **model** — cheapest that fits. Research / reading / review → `haiku` (or `sonnet`); heavy reasoning → `opus`; otherwise omit to inherit the parent. - **tools** — least privilege. Anything that **reviews / audits / researches** should be **read-only**: `Read, Grep, Glob` (+ `WebFetch, WebSearch` if it needs the web). Only add `Edit, Write, Bash` if it genuinely must change things. Assume: *if it can touch da