SDD-Design-Skill

Turn a confirmed Design Brief + UI Spec into an actual design. Implementation stage: reads the feature's UI-SPEC.md (the UI design and whatever visual values it committed to, resolved from the design guideline) and DESIGN-BRIEF.md (the acceptance-criteria scenarios), plus UL-MAP.md / DESIGN-FOUNDATIONS.md, then builds real screens and interactions via one of two targets: Figma (through the connected Figma MCP) or self-contained HTML+CSS files. Honors every value the spec fixed; for visual details the spec deliberately left open, commits sensible choices at build time (consistent with the guideline / foundations) and lists them — without re-asking for a design guideline. Verifies every acceptance-criteria scenario in the brief is realized. Triggered by: "design-build", "build the design", "生成設計", "實作設計", "/design-build".

Manage a Ubiquitous Language Map for design — the single shared vocabulary that bridges the user's/domain term, the component or pattern name, the user-facing UI label, and the design token, within one product area. Optional and best run *after* ui-spec has settled the screens, components, labels, and visual values — to capture the vocabulary the design actually landed on — then kept in sync as later features and design-build introduce new components, labels, and states. Recommended when the vocabulary will be reused across features; skippable for a one-off. Use when: initializing a new map, or updating/reconciling an existing one. Triggered by: "ubiquitous language", "UL map", "設計語言", "共用語言", "design glossary", "/ul-init", "/ul-update".

Two modes: (1) FEATURE — take a confirmed Design Brief and work out the full UI design with the user: for each screen, which elements exist (buttons, inputs, lists, content blocks), their positions and hierarchy, the states (default/empty/loading/error/success), the interactions, and the visual/UI details that matter for the feature — resolved against the user's design guideline where one exists. This is where the UI is actually decided, so it is free to commit to concrete visual values (color usage, sizing, spacing, radius, type, borders) whenever they are what the discussion is about; it asks the UI questions the feature calls for rather than a fixed checklist. Generates a UI-SPEC.md focused purely on UI concerns. It contains NO scenarios and NO Given/When/Then — acceptance criteria live solely in the Design Brief; ui-spec only references them for coverage. (2) FOUNDATIONS — analyze UL-MAP.md and existing design to produce or update .sdd/DESIGN-FOUNDATIONS.md (layout system, component inventory, interaction

Reach 100% intent consensus with the user on a design problem — the user's intent, the underlying need, the target UX experience, and the end-to-end user flow — then pin it down with concrete flow scenarios that cover the happy path, boundaries, and exceptions. These scenarios double as the feature's acceptance criteria — this brief is the single home for all requirement examples and AC; downstream skills consume them, never restate them. Compile a Design Brief written purely in user/experience language for handoff to ui-spec. Produces no design artifacts and edits no files other than the brief. Triggered by: "ux-spec", "探討需求", "設計探索", "UX 探索", "/ux-spec".