/design-component
Generate a single component using existing design-system.md tokens. Skips inspiration browsing — fast path for isolated UI elements.
$ npx -y skills add fusengine/agents --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/design-component
Context preview
What this command does when you run it.
Generate a single component using existing design-system.md tokens. Skips inspiration browsing — fast path for isolated UI elements.
Command definition
design-component.mdname: design-component
description: "Generate a single component using existing design-system.md tokens. Skips inspiration browsing — fast path for isolated UI elements."
/design:component — Single Component (COMPONENT scope)
Generate one UI component using existing design tokens.
**Complete documentation**: `skills/design-web/SKILL.md` (or `skills/design-webapp/SKILL.md` for an app-specific pattern like a data table or command palette).
Usage
/design:component pricing card with 3 tiers
/design:component testimonial carousel
/design:component data table with sorting
Prerequisites
`design-system.md` must exist at project root. If missing, use `/design` instead.
Workflow
1. Read `design-system.md` — this is the single source of truth for tokens. 2. No inspiration browsing (COMPONENT scope skips it per `design-method`'s routing table). Optionally search `skills/design-web/references/21st-dev.md` or `shadcn.md` for pattern inspiration. 3. Generate the component directly as HTML/CSS from `design-system.md` tokens, following `skills/design-web/references/component-variants-ref.md` for size/state/color variants. 4. Read `skills/design-motion/SKILL.md` — gate micro-interactions; mandatory hover/focus/disabled states regardless. 5. Read `skills/design-review/SKILL.md`, component-scoped: contrast, forbidden fonts, OKLCH-only, all states present, light+dark screenshot of the component in isolation.
Forbidden
Creating a new `design-system.md`. Inspiration browsing (use the search tools above instead). Skipping light+dark validation.
Read more
name: design-component description: "Generate a single component using existing design-system.md tokens. Skips inspiration browsing — fast path for isolated UI elements."
/design:component — Single Component (COMPONENT scope)
Generate one UI component using existing design tokens.
**Complete documentation**: `skills/design-web/SKILL.md` (or `skills/design-webapp/SKILL.md` for an app-specific pattern like a data table or command palette).
Usage
/design:component pricing card with 3 tiers /design:component testimonial carousel /design:component data table with sorting
Prerequisites
`design-system.md` must exist at project root. If missing, use `/design` instead.
Workflow
1. Read `design-system.md` — this is the single source of truth for tokens. 2. No inspiration browsing (COMPONENT scope skips it per `design-method`'s routing table). Optionally search `skills/design-web/references/21st-dev.md` or `shadcn.md` for pattern inspiration. 3. Generate the component directly as HTML/CSS from `design-system.md` tokens, following `skills/design-web/references/component-variants-ref.md` for size/state/color variants. 4. Read `skills/design-motion/SKILL.md` — gate micro-interactions; mandatory hover/focus/disabled states regardless. 5. Read `skills/design-review/SKILL.md`, component-scoped: contrast, forbidden fonts, OKLCH-only, all states present, light+dark screenshot of the component in isolation.
Forbidden
Creating a new `design-system.md`. Inspiration browsing (use the search tools above instead). Skipping light+dark validation.
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other commands on fusengine-agents.
- /apex-quick
Quick Flow for simple fixes - Single expert handles explore, code, review, and validate in one pass. Inspired by BMAD Barry.
Open command - /apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
Open command - /cleanup-context
Memory optimization - removes duplicates, consolidates knowledge, and cleans memory banks for better performance.
Open command - /create-pull-request
Auto-generate Pull Request with comprehensive description, test plan, and changelog. Uses gh CLI for creation.
Open command - /deep-code-analysis
Comprehensive codebase investigation using research-expert for documentation, explore-codebase for structure, and deep analysis. Perfect for understanding complex systems.
Open command - /epct
Systematic Explore-Plan-Code-Test methodology for structured development. Ensures comprehensive approach to feature implementation.
Open command

