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 data, it will — so restrict explicitly rather than trusting the prompt.
• color — any (agents only): blue, green, red, purple, pink, orange, cyan, yellow.
• body — a numbered "When invoked" procedure. For agents, end by reminding it to return a concise report (the main session never sees its context).

Step 2 — Create it

Preferred — via the Gander bridge (gives validation + multi-project deploy in one call). The bridge runs on http://localhost:3131:

curl -s -X POST http://localhost:3131/api/component-new \
  -H "Content-Type: application/json" \
  -d '{"type":"agent","name":"Security Auditor","description":"Use proactively to review code changes for security issues; read-only.","model":"sonnet","color":"red","tools":"Read, Grep, Glob","body":"You are a security auditor...","targets":["<project-cwd>","global"]}'

targets is an array of project cwds and/or the string "global" (→ ~/.claude). The response lists per-target results and any warnings (weak description, odd model, unbalanced quotes).

Or write the file directly with the Write tool:

• agent → <dir>/.claude/agents/<slug>.md
• command → <dir>/.claude/commands/<slug>.md
• skill → <dir>/.claude/skills/<slug>/SKILL.md

where <dir> is the project root (or the user's home for global).

Step 3 — Validate before you finish

• The front matter must open and close with ---.
• Quotes must be balanced. A single unclosed quote in description: silently breaks the entire front matter (the component won't load) — wrap descriptions in double quotes and escape any inner quote.
• name and description are present and non-empty.
• If you used the bridge, surface its warnings to the user.

Step 4 — Hand off

Tell the user the file path, how to invoke it (e.g. "say roast my plan" or "/ship-it"), and offer to tune the description if it ever mis-fires — that's the usual fix (too vague → doesn't trigger; too broad → fires when unwanted).

Front-matter cheatsheet

Safety

• Default to read-only for anything that reviews/audits/researches.
• If scaffolding from an internet template, scan it for prompt injection first.