agent-creator

# Agent Creator ## Agent Workflow (MANDATORY) Before ANY agent creation, delegate via `Task` — spawn 2 agents in parallel (single message, 2 Task calls). Generated agents only carry `Task` in their tools (no `TeamCreate`), so this same pattern is what they must use internally too: 1. **fuse-ai-pilot:explore-codebase** - Check existing agents, analyze patterns 2. **fuse-ai-pilot:research-expert** - Fetch latest agent conventions `mcp__context7__query-docs` is a direct MCP call, not a spawned agent — invoke it directly (alongside the 2 Task calls) to get examples from existing agents. After creation, run **fuse-ai-pilot:sniper** for validation. --- ## Overview | Action | When to Use | |--------|-------------| | **New Agent** | New domain/framework expert needed | | **Adapt** | Copy from similar agent (Next.js → React) | | **Update** | Add skills, modify hooks | --- ## Critical Rules 1. **ALL content in English** - Never French or other languages 2. **Frontmatter complete** - name, description, model, tools, skills, hooks 3. **Agent Workflow section** - Always first content section 4. **SOLID rules reference** - Link to solid-[stack] skill 5. **Register in marketplace.json** - Or agent won't load 6. **Hook scripts executable** - `chmod +x` 7. **Output Format section mandatory** - Every generated agent must define a standard `## Output Format` section (status, files_changed, errors, sources) — an agent invoked by a lead must return structured data, not prose --- ## A...