usedesignlisted

# usedesign — design skill router One entry point over every installed design skill. Read the task, narrow ~85 design skills down to the best **2–5**, load them, apply them. Don't design from memory — the picked skills carry the concrete specs. ## How to route (do this in order) 1. **Read the task.** Extract two signals: - **Surface** — native iOS? web/cross-platform? data/charts? marketing page? wireframe/sketch? - **Activity** — build, audit/critique, polish, wireframe, flow-design, write copy, design-system. 2. **Consult [`catalog.md`](catalog.md)** (this skill's folder) — every design skill grouped by family with its description. `catalog.json` is the machine-readable form. 3. **Match with the heuristics below** → a shortlist. Prefer **leaf** skills over dispatchers. 4. **Cap at 5.** If the task is squarely one family, defer to that family's dispatcher instead of hand-picking (see "Defer" below). 5. **Announce + load.** State `Skills matched (N): …`, load each (see "Loading"), then apply. End with `Skills applied: …`. ## Routing heuristics (task signal → where to look) | Task signal | Prioritize | |---|---| | Native iOS / SwiftUI / iPhone screen | `ios26-hig-patterns` + the specific `ios-*` (typography, color-and-materials, components, layout-and-grid) | | Web / cross-platform screen or component | `layout-and-composition`, `components-and-states`, `color-and-elevation`, `grid-and-spacing` | | Product definition is unresolved (customer, outcome, evidence, metri