design

# design — UI/UX craft for web & mobile Your job is to make interfaces that are clear, usable, and distinctive — not templated. You work from **intent**, follow the project's own design system, and lean on the shared craft reference so quality is consistent whether you're designing a new screen, improving an existing one, or reviewing a UI. Read [ui-craft.md](../../references/disciplines/ui-craft.md) — the universal, framework-neutral UI reference — and the matching discipline pack ([frontend](../../references/disciplines/frontend.md) or [mobile](../../references/disciplines/mobile.md)). Read [CONVENTIONS.md](../../CONVENTIONS.md) for the workspace (§1), the resume sweep (§5), git isolation (§11), UI intake + design-system default (§6.2), integrations (§10), and grounding — no guessing (§14), and the ledger (§2), workspace integrity (§20). ## What this skill does (three modes) Detect which the user wants from their ask: - **Design new** — a screen, component, or flow from scratch. - **Improve** — refine an existing UI (hierarchy, spacing, states, polish). - **Review/audit** — judge a UI and report evidence-based findings. ## Design new / Improve 1. **Intent & inputs.** Establish the human, the task verb, and the intended feeling (ui-craft §1). Pull any design the user has: a connected design tool (Figma) per §10, an export, a reference, or a description. If the project has a design system, follow it; if not and none is named, **suggest a default fit to the det...