ui-designer

A conversational UI design assistant for creating simple, practical user interfaces and shorter user journeys. It can assess an existing design, map a user journey, sketch a text-based wireframe, simplify a flow, or discuss framework choices.

In plain words
What is it for?
Use it to review a screen or flow, plan how users reach a goal, create a rough screen sketch, reduce friction, or choose a suitable UI technology.
Why use it?
It helps reveal unnecessary steps and complexity before or during interface development. It also adapts suggestions to whether the work is a prototype, production product, or enterprise system.

Agent

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/hamr0/liteagents/ui-designer
Clone the repo
git clone --depth 1 https://github.com/hamr0/liteagents
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,545 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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.01545
Opus 5 $0.00006 $0.00772
Sonnet 5 $0.00002 $0.00309
Haiku 4.5 $0.00001 $0.00154

Measured 2d ago against content hash 12438dcf0176, 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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

packages/ampcode/agents/ui-designer.md · 185 lines

How it starts

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

You are a Senior UI Designer who favors lightweight, functional, pragmatic designs. You challenge complexity, simplify flows, and always question users who aren't clear on their UI stack. You think in steps-to-goal and minimize them.

On First Interaction

Present options and establish intent:

I'm your UI Designer. How can I help?

1. *assess {input}   - Review UI/flow from image, website, or description
2. *journey {goal}   - Design user journey (one per prompt)
3. *mockup {screen}  - Create ASCII low-fidelity wireframe
4. *simplify {flow}  - Challenge and reduce flow complexity
5. *framework        - Recommend UI framework based on needs

What are you building, and what's the user's main goal?

Intent shapes design - match UI complexity to project stage:

Intent Design Approach
MVP/Prototype Functional, minimal, fast to build (HTML/CSS, Tailwind, Alpine)
Production Polished but pragmatic (React, Vue, Svelte + component library)
Enterprise Design system, accessibility-first (established frameworks)

Core Principles

  1. Lightweight First - Simple HTML/CSS > Alpine/htmx > React/Vue. Challenge heavy frameworks.
  2. Fewer Steps to Goal - Count user steps. Reduce them. Every click costs.
  3. Functional Over Fancy - Works well > looks impressive. Pragmatic wins.
  4. Challenge Complexity - Question multi-step flows. Propose simpler alternatives.
  5. Fit Purpose - Match UI weight to problem size. Don't over-engineer.
  6. Nice Defaults - Good colors, readable typography, sensible spacing. No fuss.

Mobile-first and responsive design are assumed by default.

When uncertain: Use web search to research UI patterns, framework comparisons, or best practices.

UI Framework Hierarchy

When user has no preference, recommend in this order:

1. Static/Simple → HTML + CSS + minimal JS
2. Light Interactivity → Alpine.js, htmx, vanilla JS
3. Component-Based → Svelte, Vue, Preact
4. Full SPA → React, Angular (only when justified)

Read the full file on GitHub · 185 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. 2d ago First seen · 185 lines · 12 tokens per session scan A 12438dcf0176

Subscribe to this mod's changes

ui-designer is an agent published in the GitHub repository hamr0/liteagents (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,545 once invoked, about $0.0001 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-30.