UX/UI Agent Skills is a set of instructions, design tokens, reusable components, accessibility rules, and design-system references that guide Claude in producing interface designs and code. It is intended for developers and designers who want framework-independent, token-based UI work with accessibility checks. The catalogue entries package these UX, UI, component, and validation workflows as Claude Code skills and related add-ons.
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.
npx skills add plugin87/ux-ui-agent-skills --skill design-componentgit clone --depth 1 https://github.com/plugin87/ux-ui-agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/plugin87/ux-ui-agent-skills/design-component)<a href="https://agentmods.dev/skills/plugin87/ux-ui-agent-skills/design-component"><img src="https://agentmods.dev/badge/skills/plugin87/ux-ui-agent-skills/design-component/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/plugin87/ux-ui-agent-skills/design-component"><img src="https://agentmods.dev/badge/skills/plugin87/ux-ui-agent-skills/design-component.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.1 | $0.00079 | $0.02805 |
| Opus 5.5 | $0.00032 | $0.01122 |
| Sonnet 5.5 | $0.00016 | $0.00561 |
| Haiku 4.5 | $0.00008 | $0.00281 |
Grade A, and why
design-component 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 18d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Design Component
Step 0 — is the kit here? This skill reads files from the kit. Check once:
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSINGOnKIT_MISSINGonly the skill folders were installed, which is whatnpx skills adddoes. Say so plainly, point the user atnpx ux-ui-agent-skills initor the plugin install, and stop. Do not guess the contents of a file you could not open.
Produce a complete component specification matching the project format.
Steps
- Read
.claude/rules/components.md→ "Component Quality Bar" (the 8-state table) and "Atomic Design"; the always-on 8-state table is inCLAUDE.md→ Non-Negotiables. - Check if it already exists:
${CLAUDE_SKILL_DIR}/../../../components/atoms.md,molecules.md,organisms.md,templates.md,navigation.md,feedback.md,forms-advanced.md,overlays.md. Match the existing spec format. - Pull the ARIA pattern from
${CLAUDE_SKILL_DIR}/../../../accessibility/aria-patterns.mdand contrast/target rules from${CLAUDE_SKILL_DIR}/../../../accessibility/wcag-checklist.md. - Map every value to tokens (
${CLAUDE_SKILL_DIR}/../../../tokens/*.json) — sizes viasizing.json, states viastates.json. - Apply visual judgment from
${CLAUDE_SKILL_DIR}/../../../taste/design-taste.md(states, focus, no slop). - Optional fast start:
python3 ${CLAUDE_SKILL_DIR}/../../../scripts/scaffold_component.py "<Name>"to emit a stub, then fill it in.
Output
Spec with: anatomy diagram, variants table, sizes table, all 8 applicable states, token mapping, accessibility (role/keyboard/SR), and a note to render via ${CLAUDE_SKILL_DIR}/../../../frameworks/adapter-protocol.md.
Accuracy — verify every state, don't assume (mandatory when code is produced)
A component is only "correct" when every variant × state renders right — not just the resting default. Build a states harness: render the component in each applicable state (default, hover, focus, active, disabled, loading aria-busy, error aria-invalid, selected aria-pressed/aria-selected) × each variant in one HTML file (see ${CLAUDE_SKILL_DIR}/../../../examples/component-states/button.html). Then RUN the gates and report their real output (CLAUDE.md → Verification Protocol):
node ${CLAUDE_SKILL_DIR}/../../../scripts/verify_states.mjs <harness> [--dark]— contrast of every element in default/hover/focusnode ${CLAUDE_SKILL_DIR}/../../../scripts/axe_audit.mjs <harness> [--dark]— ARIA/role/name/label correctnessnode ${CLAUDE_SKILL_DIR}/../../../scripts/measure_render.mjs <harness> [--dark]— every text element AA- overlays/modals also:
node ${CLAUDE_SKILL_DIR}/../../../scripts/verify_focustrap.mjs <harness> --open=<trigger>Every state must pass in light AND dark before the component is "done". Never claim a state is correct without a gate proving it.
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.
- 18d ago Changed · +6 lines f6c0510ac26d
- 1mo ago First seen · 80 lines · 79 tokens per session scan A e35325764a67
design-component is a skill published in the GitHub repository plugin87/ux-ui-agent-skills (2,979 stars, last pushed 5d ago), licensed MIT. It adds 79 tokens to every session and 2,805 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
component-family-consistency
Buttons, inputs, badges and pills share radius, colour logic, shadow, border and spacing. Use when building or reviewing a component library.
extract-design
Extract colours, typography, spacing, components and W3C design tokens from a live website with Dembrandt. Use when you need a site's real tokens or want to seed a design system from it.
modular-scale-typography
Ratio-based type scale where every size relates to the others. Use when defining font sizes or type tokens, or when typography feels arbitrary.
data-display-and-selection
View modes, row selection, mass actions, sorting, filters, search and table patterns. Use when designing data tables, listings, file browsers or any collection.
modal-and-overlay-patterns
Modals, drawers, bottom sheets and popovers, each with its scope and blocking level. Use when designing dialogs, confirmations, side panels or action sheets.