A command that turns a UI specification document into HTML, CSS, and JavaScript prototypes. It can also use a website, image, or named style as a visual reference.

Use it to create early website or app prototypes from `docs/UI_SPEC.md`, copy the look of a reference site or image, and save the results in `docs/prototypes/`.

It removes the need to turn written interface requirements into an initial visual mock-up by hand. It also connects design choices to the intended user journey and emotions described in the specification.

How nguyennguyenit/MultiClaude configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to nguyennguyenit/MultiClaude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/nguyennguyenit/MultiClaude/master/.claude/commands/ipa/design.md

Clone the repo

git clone --depth 1 https://github.com/nguyennguyenit/MultiClaude

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/nguyennguyenit/multiclaude/design/github.svg)](https://agentmods.dev/commands/nguyennguyenit/multiclaude/design)

Your own site

<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/design"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/design/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/design"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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 3,955 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00012	$0.03955
Opus 5.5	$0.00005	$0.01582
Sonnet 5.5	$0.00002	$0.00791
Haiku 4.5	$0.00001	$0.00396

Measured 2mo ago against content hash 7d662bb00728, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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/ipa/design.md · 519 lines

How it starts

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

Purpose

Generate production-ready HTML/CSS/JS prototypes from docs/UI_SPEC.md.

Key Features:

CJX-driven design (emotions → UI decisions)
Reference cloning (URL/image)
UI/UX Pro Max skill integration

Output: docs/prototypes/ (HTML, CSS, JS, icons)

Input

Required:

docs/UI_SPEC.md (must exist from /ipa:bd, includes CJX)

Optional Reference: $ARGUMENTS

Reference can be:

URL: Website to clone design from (e.g., https://example.com)
Image: Screenshot or design file path (e.g., ./design.png)
Style: Preset name (e.g., minimalist, glassmorphism)

CJX → Design Mapping

Read CJX from UI_SPEC.md and apply to design decisions:

┌─────────────────────────────────────────────────────────────┐
│ CJX-DRIVEN DESIGN                                           │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│ JOURNEY STAGE → DESIGN PATTERN                              │
│                                                             │
│ Discovery (Curious)                                         │
│   → Bold hero, trust signals, clear value prop              │
│   → Primary CTA prominent, social proof visible             │
│   → Animation: subtle entrance, draw attention              │
│                                                             │
│ Onboarding (Hesitant)                                       │
│   → Progress indicator, minimal fields                      │
│   → Reassuring copy, easy exit option                       │
│   → Animation: encouraging micro-interactions               │
│                                                             │
│ Usage (Engaged)                                             │
│   → Clean dashboard, quick actions                          │
│   → Data visualization, status feedback                     │
│   → Animation: smooth transitions, success celebrations     │
│                                                             │
│ Retention (Satisfied/Frustrated)                            │
│   → Help accessible, feedback channels                      │
│   → Achievement badges, usage stats                         │
│   → Animation: reward animations, gentle nudges             │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Read the full file on GitHub · 519 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.

2mo ago First seen · 519 lines · 12 tokens per session scan A 7d662bb00728

Subscribe to this mod's changes

design is a command published in the GitHub repository nguyennguyenit/MultiClaude (23 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 3,955 once invoked, about $0.0000 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.

CSS and styling Design and UX Frontend

design next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
designnguyennguyenit/MultiClaude	Command	23	2mo ago	MIT	A	12	Claude Code
ux-recommendLaith0003/ux-skill	Command	96	4d ago	MIT	A	17	Claude Code
color-specialistimsaif/design-with-claude	Command	11	yesterday	MIT	A	35	Claude Code
responsive-design-specialistimsaif/design-with-claude	Command	11	yesterday	MIT	A	36	Claude Code
revisar-uiluanpdd/kit-mcp	Command	5	4d ago	MIT	A	19	Claude Code
bolderqorstack/qorstack-report	Command	42	17d ago	none	A	0	Claude Code
frontend-designqorstack/qorstack-report	Command	42	17d ago	none	A	0	Claude Code

MultiClaude: Command for Claude Code