senmu-build-designlisted
Install: claude install-skill SenMuShare/senmu-buildos
# 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: [Prototypes](references/prototype-exploration-and-interface-review.md).
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. Govern cross-page gaps only; keep one-offs 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/emp