A UI and UX design assistant for planning how websites, apps, and game interfaces look and work. It chooses a design role such as UX designer or game UI designer for each request.

Use it for user flows, wireframes, design systems, accessibility guidance, component specifications, and game interface elements such as health bars or inventory screens.

It keeps design guidance focused on the type of interface being made, instead of mixing unrelated design concerns together.

ui — Skill by P47Phoenix

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/p47phoenix/claude-plugins/ui

Any agent

npx skills add P47Phoenix/Claude-Plugins --skill ui

Clone the repo

git clone --depth 1 https://github.com/P47Phoenix/Claude-Plugins

Made for: Claude Code, Codex.

Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,288 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00110	$0.02288
Opus 5	$0.00055	$0.01144
Sonnet 5	$0.00022	$0.00458
Haiku 4.5	$0.00011	$0.00229

Measured 2d ago against content hash 0815aadd6262, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ui scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

delivery-team/skills/ui/SKILL.md · 223 lines

How it starts

The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UI/UX Design Agent

Design Principle: Role Context Isolation

This skill keeps design-specific knowledge out of the main context window. When a design task is requested, the relevant role is detected, only the corresponding reference file(s) are loaded, and a sub-agent is spawned with that isolated context. The main context receives only the finished design artifact.

Design tasks frequently span concerns -- a component specification may need both design system tokens and accessibility guidelines simultaneously. This skill follows the godot pattern: multiple overlapping references loaded into a single sub-agent when the task warrants it.

Phase 1: Role Detection

Detect the relevant designer role from (in priority order):

Explicit role mention -- "as a UX designer", "from a UI perspective", "game UI design"
Task type signals -- see role manifests below
Domain signals -- game-related keywords (HUD, minimap, health bar, inventory UI, quest log, crafting UI) route to Game UI Designer; application/web keywords (design system, WCAG, component spec, form patterns) route to UI Designer; research/flow keywords (persona, journey map, usability testing, card sorting) route to UX Designer
Artifact signals -- wireframe or flow diagram request -> UX Designer; visual mockup or token spec -> UI Designer; HUD layout or game menu -> Game UI Designer

If ambiguous, ask before proceeding. Do not assume.

Declare before every task:

Role: [ROLE] | Task: [TYPE] | References: [list of reference files]

Role Routing Table

Load only the matched role manifest. Each manifest contains the full task-type routing table, instructions, and guardrails for that role.

Role	Manifest	Detection Cue
UX Designer	`references/roles/ux-designer.md`	flow / journey / research / wireframe / IA
UI Designer	`references/roles/ui-designer.md`	design system / tokens / component / WCAG / interaction
Game UI Designer	`references/roles/game-ui-designer.md`	HUD / game menu / inventory / dialog / game accessibility

Read the full file on GitHub · 223 lines

Files

What ships with it

20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 223 lines · 110 tokens per session scan A 0815aadd6262

Subscribe to this mod's changes

ui is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 110 tokens to every session and 2,288 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Design and UX

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens