How do I install the Senmu Build Design skill?

Run npx skillmds@latest add senmushare/senmu-build-design in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Senmu Build Design safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Senmu Build Design?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Senmu Build Design free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Senmu Build Design?

SenMuShare (@senmushare) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Senmu Build Design by senmushare — Agent Skill

Name: Senmu Build Design
Author: SenMuShare

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.

SenMuShare Updated Sep 17, 2026

File contents

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.
Analyze/adapt a screenshot, URL, design, or interface: Reference Analysis.
Interaction, motion, accessibility, feel: Interaction.
Alternatives, prototypes, UI/UX review: Prototypes.

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.

---name: senmu-build-designdescription: 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.---# Interface DesignTurn 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.

Frequently asked questions