ux-ui-wasp-drone — Claude Code and Codex subagent
ux-ui-wasp-drone — a subagent for Claude Code and Codex that enforces a project's design system on UI and components, tracks token drift, and governs shadcn/ui, Mantine, Lucide-react, and Framer Motion integration.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install web-development-tools@wasp-nestWhat ux-ui-wasp-drone does
ux-ui-wasp-drone reads the project's design system from library/knowledge-base/<product>-ux-ui/ and handles three concerns: verifies UI against the design brief and token definitions; advises when to reach for a library (shadcn/ui, Mantine, Lucide, Framer Motion) versus writing custom code; ensures new tokens go into 01-master-tokens.css rather than scattered through the codebase.
For each review, the subagent cites the exact design-document section, shows which line to change and what token or class to use, and references the relevant library guide. Components from external libraries always go through wrappers — your own <Button>, <Icon>, <Motion> — so the system stays enforceable across upgrades.
Not for building a design system from scratch (that's design-system-wasp-drone), backend work, or asset-registry tasks.
What it helps with
- Check UI against the design brief and find pixel-level or token-level deviations
- Pick a component from shadcn/ui, Mantine, or determine when to write custom markup
- Update design documentation when a specification changes
- Audit token drift — spot repeated color, spacing, or radius values that should be one token
- Author motion, animation and transition specs
Example prompts for the agent
- Review this sign-up form against section 2.1 of
00-design-brief.md - Which Mantine component works for a dropdown menu with leading icons?
- Wrap the shadcn/ui Button primitive with our
color-action-primarytoken
How to install ux-ui-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install web-development-tools@wasp-nest2Manually: put the files in place
.claude/agents/ux-ui-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/ux-ui-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/ux-ui-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about ux-ui-wasp-drone
How do I install ux-ui-wasp-drone in Claude Code?
In Claude Code, run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install web-development-tools@wasp-nest, then open .claude/agents/ux-ui-wasp-drone.md. For Codex, open .codex/agents/ux-ui-wasp-drone.toml.
What does ux-ui-wasp-drone do?
It enforces the project's design system on UI and components: colors, spacing, component choices, motion. Advises on library selection or wrapper authoring. Detects token drift when one value appears scattered in code instead of referenced through a single token.
When should I not use ux-ui-wasp-drone?
Skip it for building a design system from scratch (use design-system-wasp-drone instead), backend work, data tasks, or asset-registry operations — those belong to other subagents.