ux-ui-svelte-wasp-drone — Claude Code subagent: Svelte UI, install
ux-ui-svelte-wasp-drone keeps the UI layer of a Svelte 5 / SvelteKit app on the project's own tokens: reviews PRs, migrates surfaces, guards the @theme bridge and tenant theming.
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-svelte-wasp-drone does
This subagent owns the UI layer of a Svelte 5 / SvelteKit codebase: shadcn-svelte 1.x on Bits UI v2 and Melt UI, Tailwind v4, the @theme bridge into project design tokens, brand or tenant theming. Ask it a UI question and it opens the governing doc first, whether that is the project's UI decision record, its token file, a brand contract or app.css. Every ruling quotes the section and a path:startLine-endLine range. No answers from memory.
The work runs in steps: Phase 0 wiring, the token bridge, copy-in components in four patterns, dark-mode polarity, white-label verification, migrating one surface, and a PR review against a list of violation classes. Edits inside copied components carry a marker comment so upstream sync stays possible. Skipping the bridge is a blocker in its book: an arbitrary-value utility such as bg-[#1c1f26] where a token exists is a bug, not styling.
Where a repo has no UI standard yet, it puts shadcn-svelte with Tailwind v4 forward as a decision for the owner instead of assuming adoption. React work, surfaces an ADR scopes out, and a design system built from scratch are handled by other agents. On Codex the same agent installs as .codex/agents/ux-ui-svelte-wasp-drone.toml.
What it helps with
- review a PR that touches markup or styling in a
.sveltefile - copy in a shadcn-svelte component without losing project tokens
- move a bespoke style onto Tailwind v4 utilities
- check that a tenant theme still resolves through a component
- swap
on:clickforonclickwhile migrating a surface
Example prompts for the agent
- Add a
Buttonfrom shadcn-svelte to the/settingspage and wire it through the token bridge. - Review this PR for arbitrary-value utilities that skip
@theme. - Migrate this bespoke panel to Tailwind v4 utilities and drop the dead
<style>block.
How to install ux-ui-svelte-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-svelte-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-svelte-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-svelte-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-svelte-wasp-drone
How do I install ux-ui-svelte-wasp-drone in Claude Code?
Use the marketplace: /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install web-development-tools@wasp-nest. The agent lands at .claude/agents/ux-ui-svelte-wasp-drone.md.
What does ux-ui-svelte-wasp-drone do?
It handles UI questions in Svelte 5 and SvelteKit: checks the work against the project's UI decision record and token file, cites the section with line numbers, and proposes the smallest fix. It also flags anything that goes around the token bridge.
Does it work for React components?
No. React UI belongs to ux-ui-wasp-drone, and a brand-new design system is the job of design-system-wasp-drone. This one stays on Svelte surfaces covered by the project's UI decision record.