# Senmu Build Design

> Define or review UI/UX direction, systems, layout, typography, color, data visualization, responsive behavior, interaction, motion, accessibility, and visual or interaction prototype validation. Not for product scope, routine implementation, library APIs, or independent audits.

- Skill: `senmushare/senmu-build-design` (Agent Skill, multi-file: 9 files)
- Install (CLI): `npx skillmds@latest add senmushare/senmu-build-design`
- Raw SKILL.md: https://api.skillmd.com/api/skills/senmushare/senmu-build-design/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Design & Media
- Author: SenMuShare (https://skillmd.com/u/senmushare)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/senmushare/senmu-build-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: [Prototypes](references/prototype-exploration-and-interface-review.md).

Read only what is needed. Implement approved designs 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/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.
- Design-library content is optional inspiration, not project fact or a default.
- Exploration is not a product decision. Write selected rules to the owner; isolate alternatives.

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