design-ui

# Design UI Design UI screens in Google Stitch and produce a Compose Implementation Blueprint with HTML + token inventories persisted for downstream skills. **Architecture Reference:** [`_shared/patterns.md`](../_shared/patterns.md) — do **not** preload this file. Read only the specific section a step explicitly cites (e.g. "Typography" in Step 1.16, Rule 13 in Step 1.17), at the moment that step runs. Every rule this skill depends on is either restated inline in the phase files or cited with its exact section name. ## Purpose `design-ui` is a **design-only** skill. It handles all Stitch MCP design work and produces a Compose Implementation Blueprint plus persisted HTML + token inventories under `.claude/docs/{featurename}/designs/extracted/`. The blueprint references project-wide rules (`patterns.md`, `m3-colors.md`, `X_COMPONENTS_CATALOG.md`) rather than restating them. It does NOT implement code or invoke other skills. After `design-ui` completes, the user can invoke `/create-feature` (new feature, no Kotlin source yet) or `/modify-feature` (existing feature, Kotlin source already exists) to implement the design. Those skills auto-detect the blueprint and enter design-aware mode. **Invocation modes:** - `/design-ui` (no args) — explicitly run Project Init for the repo - `/design-ui {featurename}` — design that **feature** (its primary screen **plus any tightly-related secondary screens** — an overlay surface like a bottom sheet/dialog, or a full sibling screen like a...