Senmu Build Design

---
name: senmu-build-design
description: "Define or review UI/UX direction, layouts, visual systems and interaction quality, including reference adaptation. Not for routine implementation under an agreed design."
---

# Interface Design

Turn experience goals into implementable decisions. Start from the interface, behavior, system, brand, and devices. Extend its design owner; never create a parallel standard.

## Route by Outcome

- Pages, redesigns, visual systems, layout, type, color, responsive rules: [Visual Systems](references/visual-systems-and-design-language.md).
- Analyze/adapt a screenshot, URL, design, or interface: [Reference Analysis](references/reference-interface-analysis-and-reconstruction.md).
- Interaction, motion, accessibility, feel: [Interaction](references/interaction-motion-and-accessibility.md).
- Alternatives, prototypes, UI/UX review or design-asset adoption: [Prototypes](references/prototype-exploration-and-interface-review.md).
- Only for optional pattern inspiration: [Pages](references/design-library/page-structures-and-visual-directions.md) or [Components](references/design-library/component-design-patterns.md); [Index](references/design-library/INDEX.md) maps choices. These are not project facts or required pre-reads.

Read only what is needed. Implement the selected or already-authorized direction under project/Engineering rules; use specialist skills for current APIs/methods only.

## Core Contract

- Establish interface type, task, context, hierarchy, assets, and constraints. If needed, offer distinct directions with a recommendation and risks.
- Express hierarchy, layout, components, tokens, states, assets, responsiveness, and verification. Adjectives are not specifications.
- Reuse project systems, brand, and components. Own new visual/interaction decisions even for one page; routine changes covered by existing design rules stay with implementation.
- Make frequent actions direct/predictable. Motion must explain feedback, state, space, or change, with reduced-motion/non-hover paths.
- Design accessibility, responsiveness, and loading/empty/error/disabled states from the start; never rely on one sensory cue.
- Deliver direction analysis with observed evidence, implementable decisions, and limits. To claim implemented visual/interaction quality, verify real rendering at affected viewports/states; code or static checks alone are insufficient.
- Exploration is not a product decision. Write selected rules to the owner; isolate alternatives. Preserve requirement-related user/AI prototypes and UI drafts with explicit adoption scope and Product's version/feature linkage; chat-only images are not durable handoff.

Handoff behavior/content/acceptance to Product, implementation contracts to Engineering, verdicts to Assurance, and release facts to Delivery.