/ui-design

Generate HTML UI mockups with optional parallel variant exploration.

Usage

bash

/ui-design yourbench "login screen"
/ui-design yourbench "dashboard" --variants 3
/ui-design coordinatr "project list" --tech shadcn
/ui-design yourbench list                    # Show existing designs

Where Designs Live

code

ideas/yourbench/docs/ui-designs/
├── login-screen-v1.html
├── login-screen-v2a.html      # Variant A
├── login-screen-v2b.html      # Variant B (approved)
├── dashboard-v1.html
└── components/
    └── button-variants.html

Why in ideas/? Designs are planning artifacts, not code.

Execution Flow

1. Parse Request

•Project (yourbench)
•Design name (login screen)
•Variant count (--variants 3)
•Technology (--tech shadcn)

2. Load Context

bash

Glob: ideas/[project]/docs/ui-designs/*.html
Read: shared/docs/style-guide.md
Read: ideas/[project]/project-brief.md

3. Generate Design(s)

Single design:

code

→ ideas/yourbench/docs/ui-designs/login-screen-v1.html

Multiple variants (parallel ui-ux-designer agents):

code

→ login-screen-v1a.html
→ login-screen-v1b.html
→ login-screen-v1c.html

4. Present Options

code

Created 3 login screen variants:

1. v1a.html - Minimal, centered form
2. v1b.html - Split screen with illustration
3. v1c.html - Card-based with social logins

View: open ideas/yourbench/docs/ui-designs/login-screen-v1a.html

Which direction? (a/b/c/iterate/combine)

5. Iterate

User requests changes:

•"Move OAuth buttons below the form"
•"Try a darker color scheme"

6. Approve

code

User: approve v1b

AI: ✓ Marked login-screen-v1b.html as APPROVED

    Reference in TASK.md:
    "Implement login per docs/ui-designs/login-screen-v1b.html"

Technology Options

Option	Description
`--tech vanilla`	Plain HTML/CSS/JS (default)
`--tech shadcn`	Styled for shadcn/ui with implementation hints
`--tech chakra`	Styled for Chakra UI

HTML Structure

Self-contained with embedded CSS/JS:

•CSS variables from style-guide.md
•Responsive breakpoints
•Interactive behaviors
•Metadata block at end (status, decisions, related specs)

Listing Designs

bash

/ui-design yourbench list

UI Designs for yourbench:
├── login-screen-v1b.html [APPROVED]
├── dashboard-v1.html [DRAFT]
└── settings-v1a.html [DRAFT]

Integration with Implementation

bash

/implement yourbench 001 1.3  # "Implement login UI"

AI: Found approved design: login-screen-v1b.html
    Implementing to match design...

Reference in TASK.md:

markdown

## Acceptance Criteria
- [ ] Matches docs/ui-designs/login-screen-v1b.html
- [ ] Responsive at 320px, 768px, 1280px

Best Practices

•Start with variants - Explore before converging
•Approve explicitly - Clear handoff to implementation
•Include metadata - Future you will thank you
•Test responsiveness - Check 320px, 768px, 1280px
•Document decisions - Why this approach?