ui-prototype

Files (1)

• SKILL.md

SKILL.md (first lines)

# UI Prototype

Answer **one** visual question with throwaway code. Keep the answer; delete the code (or isolate it so it never ships).

## When to use

- Direction adjectives still disagree
- Need to see 2–3 radically different compositions
- Hero / type / atmosphere choice needs eyes, not prose

## Process

### 1. Name the question

One sentence. If there are multiple questions, pick the highest-risk one; park the rest.

### 2. Variants

Implement **2–3 radically different** variants toggleable from one route or flag. Reuse tokens if they exist; otherwise hardcode briefly and note what should become tokens.

Obey hard rules in `docs/agents/design-rules.md` (hero budget, brand-first, no hero cards/overlays) unless the question is explicitly stress-testing one rule — say so.

### 3. Decide

Walk the user through variants; capture the decision into `DIRECTION.md` and/or `TOKENS.md` (edit those docs — don't leave the answer only in chat).

### 4. Dispose

Remove throwaway routes/components, or mark clearly under a `prototypes/` path excluded from nav/ship. **Completion criterion:** decision written to site docs; prototype cannot be mistaken for production.

From Alfred-Lau/skills, MIT.

More from Alfred-Lau/skills