# ux-ui-svelte-wasp-drone

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.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 96 repo stars
- Author: Legion Code Inc.
- License: AGPL-3.0-or-later · policy=link-only · description only; the file stays with the author
- Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/web-development-tools/agents/ux-ui-svelte-wasp-drone.md
- Updated: 2026-10-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/ux-ui-svelte-wasp-drone

## What it 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`.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add legioncodeinc/vibe-coding-tools
```
In the agent chat (not a shell):
```text
/plugin install web-development-tools@wasp-nest
```

2. **Manually: put the files in place**
- File: `.claude/agents/ux-ui-svelte-wasp-drone.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/ux-ui-svelte-wasp-drone.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/ux-ui-svelte-wasp-drone.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/web-development-tools/agents/ux-ui-svelte-wasp-drone.md

## When to use it
- review a PR that touches markup or styling in a `.svelte` file
- 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:click` for `onclick` while migrating a surface

## Example prompts
- Add a `Button` from shadcn-svelte to the `/settings` page 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.

## Similar
- [Svelte](https://affpapa.org/en/nevibecode/mcp/svelte.md) — MCP server · 1169 installs
- [Tailwind Svelte Assistant](https://affpapa.org/en/nevibecode/mcp/tailwind-svelte-assistant.md) — MCP server · 685 installs
- [shadcn-svelte](https://affpapa.org/en/nevibecode/skills/vercel-labs-shadcn-svelte.md) — skill · 1200 installs
- [svelte-llm-mcp](https://affpapa.org/en/nevibecode/mcp/khromov-svelte-llm-mcp.md) — MCP server · 910 installs
- [svelte-debug](https://affpapa.org/en/nevibecode/commands/svelte-debug.md) — command · 134 installs
- [svelte-mcp-feedback](https://affpapa.org/en/nevibecode/skills/svelte-mcp-feedback.md) — skill · 102 installs

From the same set: [legioncodeinc/vibe-coding-tools](https://affpapa.org/en/nevibecode/by/legioncodeinc/vibe-coding-tools.md) — 172 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
