hooks-smithDelegate when a Claude Code hook must be created or edited - the user wants something to run automatically at a lifecycle event (on save, before a tool, on stop), to block or validate a tool call, or to fix a hook that does not fire. Owns the event/type/matcher choice, the settings.json entry, any h
mcp-smithDelegate when a project-level MCP server must be added, configured, or debugged - the user wants to connect an MCP server, pick its transport and scope, wire its secrets via env vars, or fix one that will not connect. Owns the .mcp.json or ~/.claude.json entry and the connection check. Not for MCP b
plugin-smithDelegate when a Claude Code plugin must be scaffolded or restructured as a whole - the user wants to create a new plugin, edit its plugin.json manifest, lay out its directories, bump its version, or wire its marketplace distribution. Owns the plugin shell, manifest, and distribution plus the validat
skill-smithDelegate when a new skill or slash command must be authored or an existing SKILL.md edited - the user wants to create, build, scaffold, write, rename, refactor, or fix a skill, a /command, or its frontmatter, scope, or supporting files. Owns the skill create and update flow plus the validation gate.
subagent-smithDelegate when a subagent definition must be authored or edited - the user wants to create, build, scaffold, write, rename, or fix an agent file under .claude/agents/ or a plugin agents/ dir, tune its description so delegation fires, lock down its tools or permissions, or preload skills. Owns the sub
workflow-smithDelegate when a .workflow.js fan-out script must be created or edited - the user wants to parallelize agents at scale, build or change an orchestration that fans out subagents across phases, add a stage or schema, or wire its distribution model and wrapper SKILL.md. Owns the workflow create and upda