A UI-design workflow that turns feature requirements into wireframes, component specifications, design tokens, and interaction rules. Design tokens are named values for visual choices such as colors, spacing, and typography.

Use it to design screens, list component states and properties, define reusable visual tokens, document interactions in Given/When/Then form, and add WCAG AA accessibility notes.

It connects the interface design to specific user stories and accessibility requirements before implementation. A sign-off gate records the user's approval of the design.

amby.design — Command for Claude Code by ambystechcom: A UI-design workflow that turns feature requirements into wireframes…

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 commands/ambystechcom/ambykit/amby.design

Clone the repo

git clone --depth 1 https://github.com/ambystechcom/AmbyKit

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ambystechcom/ambykit/amby.design.svg)](https://agentmods.dev/commands/ambystechcom/ambykit/amby.design)

Your own site

<a href="https://agentmods.dev/commands/ambystechcom/ambykit/amby.design"><img src="https://agentmods.dev/badge/commands/ambystechcom/ambykit/amby.design.svg" alt="Measured on agentmods" height="20"></a>

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 408 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.00020	$0.00408
Opus 5	$0.00010	$0.00204
Sonnet 5	$0.00004	$0.00082
Haiku 4.5	$0.00002	$0.00041

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

Security

Grade A, and why

amby.design 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 3d 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.

.claude/commands/amby.design.md · 26 lines

What it actually says

Act as the UX Designer in @.amby/roles/ux.md and say so in your first line. If $ARGUMENTS contains --as <id>, use @.amby/roles/<id>.md instead; if that file is missing, stop and list the files in .amby/roles/.

Design the UI for feature $ARGUMENTS (default: the current feature).

Context: read that feature's spec.md, the templates @.amby/templates/ui.md + @.amby/templates/design-tokens.json, and — for detailed rules — @.amby/reference/design-conventions.md. Design for the spec's user stories.

Write ui.md following the template: per story, a layout/wireframe (ASCII or embedded SVG), a component inventory (props + full state set + token names), interaction criteria in Given/When/Then tied to the US-#, and content/accessibility notes (WCAG AA).
Write/extend design-tokens.json in three tiers — primitive → semantic → component. In ui.md cite semantic/component token names, never raw values.
Keep the UI consistent with any constitution UX principle (cite by number).
Sign-off gate: present the design and ask the user to approve. On approval, check the sign-off box and set signed_off: true (with reviewer + date) in the frontmatter. Until then it's a draft.

Downstream phases treat a signed-off UI as binding.

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.

3d ago First seen · 26 lines · 20 tokens per session scan A 8b8d5ee9c030

Subscribe to this mod's changes

amby.design is a command published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 408 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-31.

Design and UX agent-skills agentic-coding agentic-workflow ai-coding ai-tools spec

amby.design

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

oss-docs

release-update

github

release

harness

e2e