agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Use when building or editing shadcn/ui components, mapping Radix vs Base UI APIs, or choosing a composition pattern (asChild vs render).
$ npx -y skills add fusengine/agents --skill shadcn-components --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/shadcn-componentsContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when building or editing shadcn/ui components, mapping Radix vs Base UI APIs, or choosing a composition pattern (asChild vs render).
name: shadcn-components description: "Use when building or editing shadcn/ui components, mapping Radix vs Base UI APIs, or choosing a composition pattern (asChild vs render)." versions: shadcn-ui: "2.x" radix-ui: "1.x" base-ui: "1.x" user-invocable: true allowed-tools: Read, Write, Edit, Glob, Grep, Task, mcp__shadcn__search_items_in_registries, mcp__shadcn__view_items_in_registries, mcp__shadcn__get_item_examples_from_registries, mcp__shadcn__get_add_command_for_items references: references/radix-components.md, references/baseui-components.md, references/templates/dialog-example.md related-skills: shadcn-detection, shadcn-registries
<objective> Documents component patterns for shadcn/ui with both Radix UI and Base UI primitives — API differences, 1:1 mapping between primitives (Dialog/Select/Tooltip/Accordion/Popover/Menu), and the two composition patterns (`asChild` for Radix, `render` for Base UI).
Requires detecting the project's primitive first (`shadcn-detection`) and consulting the shadcn MCP for registry source instead of hand-writing component internals. </objective>
Before component work, spawn agents in parallel, one `Agent` call each with a `name`:
1. **fuse-ai-pilot:explore-codebase** - Find existing components 2. **fuse-ai-pilot:research-expert** - Verify component APIs via Context7 3. **mcp__shadcn__search_items_in_registries** - Search available components
After: Run **fuse-ai-pilot:sniper** for validation.
---
| Feature | Description | |---------|-------------| | **Radix primitives** | Default shadcn/ui since 2021 | | **Base UI primitives** | New option since late 2025 | | **Component mapping** | 1:1 mapping between both | | **API differences** | asChild vs render, naming |
---
1. **ALWAYS detect primitive** before component work (shadcn-detection) 2. **ALWAYS consult MCP** before adding any component 3. **NEVER mix** Radix and Base UI APIs in same component 4. **MATCH composition** pattern to detected primitive 5. **USE registry source** as truth, not manual code
---
components/ui/ ├── dialog.tsx # Adapted to detected primitive ├── select.tsx ├── accordion.tsx └── ...
-> See [dialog-example.md](references/templates/dialog-example.md) for complete component
---
ALWAYS consult shadcn MCP before adding components:
mcp__shadcn__search_items_in_registries -> find component mcp__shadcn__view_items_in_registries -> view source mcp__shadcn__get_add_command_for_items -> get install command
---
| Component | Radix Part | Base UI Part | |-----------|-----------|--------------| | Dialog | `DialogContent` | `Dialog.Popup` | | Dialog | `DialogOverlay` | `Dialog.Backdrop` | | Select | `SelectContent` | `Select.Positioner` + `Select.Popup` | | Tooltip | `TooltipContent` | `Tooltip.Positioner` + `Tooltip.Popup` | | Accordion | `AccordionContent` | `Accordion.Panel` | | Popover | `PopoverContent` | `Popover.Positioner` + `Popover.Popup` | | Menu | `DropdownMenuContent` | `Menu.Positioner` + `Menu.Popup` |
---
<Dialog.Trigger asChild> <Button variant="outline">Open</Button> </Dialog.Trigger>
<Dialog.Trigger render={<Button variant="outline" />}>
Open
</Dialog.Trigger>---
| Topic | Reference | When to Consult | |-------|-----------|-----------------| | **Radix APIs** | [radix-components.md](references/radix-components.md) | Building with Radix primitives | | **Base UI APIs** | [baseui-components.md](references/baseui-components.md) | Building with Base UI primitives |
| Template | When to Use | |----------|-------------| | [dialog-example.md](references/templates/dialog-example.md) | Creating Dialog components |
---
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every…
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional…
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).