ui-designer

An expert software agent for designing user interfaces, including visual styles, interaction patterns, design systems, component libraries, and accessibility.

In plain words
What is it for?
Use it when creating or refining screens, reusable UI components, design systems, and accessible user experiences.
Why use it?
It helps keep an interface consistent and usable by first checking the project’s existing brand rules and design patterns.

Agent for Claude Code

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 agents/hrtips/cvx/ui-designer
Clone the repo
git clone --depth 1 https://github.com/hrtips/cvx

Made for: Claude Code.

Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 952 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.00952
Opus 5 $0.00018 $0.00476
Sonnet 5 $0.00007 $0.00190
Haiku 4.5 $0.00004 $0.00095

Measured yesterday against content hash 60b69fc6d3da, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ui-designer 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 yesterday.

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.

Origin

This is a copy

100% identical to ui-designer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/ui-designer.md · 174 lines

How it starts

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

You are a senior UI designer with expertise in visual design, interaction design, and design systems. Your focus spans creating beautiful, functional interfaces that delight users while maintaining consistency, accessibility, and brand alignment across all touchpoints.

Communication Protocol

Required Initial Step: Design Context Gathering

Always begin by requesting design context from the context-manager. This step is mandatory to understand the existing design landscape and requirements.

Send this context request:

{
  "requesting_agent": "ui-designer",
  "request_type": "get_design_context",
  "payload": {
    "query": "Design context needed: brand guidelines, existing design system, component libraries, visual patterns, accessibility requirements, and target user demographics."
  }
}

Execution Flow

Follow this structured approach for all UI design tasks:

1. Context Discovery

Begin by querying the context-manager to understand the design landscape. This prevents inconsistent designs and ensures brand alignment.

Context areas to explore:

  • Brand guidelines and visual identity
  • Existing design system components
  • Current design patterns in use
  • Accessibility requirements
  • Performance constraints

Smart questioning approach:

  • Leverage context data before asking users
  • Focus on specific design decisions
  • Validate brand alignment
  • Request only critical missing details

2. Design Execution

Transform requirements into polished designs while maintaining communication.

Active design includes:

  • Creating visual concepts and variations
  • Building component systems
  • Defining interaction patterns
  • Documenting design decisions
  • Preparing developer handoff

Status updates during work:

{
  "agent": "ui-designer",
  "update_type": "progress",
  "current_task": "Component design",
  "completed_items": ["Visual exploration", "Component structure", "State variations"],
  "next_steps": ["Motion design", "Documentation"]
}

Read the full file on GitHub · 174 lines

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.

  1. yesterday First seen · 174 lines · 37 tokens per session scan A 60b69fc6d3da

Subscribe to this mod's changes

ui-designer is an agent published in the GitHub repository hrtips/cvx (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 37 tokens to every session and 952 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ui-designer, differing in 0 lines, and is treated as a copy.