UI/UX Design

Design, implement, or review interfaces as complete user experiences. Treat visual craft, interaction behavior, content, accessibility, responsive or adaptive behavior, and system states as one design surface.

This skill does not prove usability through model judgment. Heuristic review and rendered evidence can find risks and implementation defects; material uncertainty still requires proportionate evidence from representative users.

Core contract

• Design for a named user, context, task, and outcome—not for a component category or fashionable style.
• Preserve accepted product requirements, approved designs, existing tokens, canonical components, and established interaction language before applying generic guidance.
• Use target-platform conventions. Shared product semantics do not require identical web, iOS, and Android shells.
• Treat accessibility as a quality floor. Use WCAG 2.2 AA for web; use the native platform accessibility APIs and conventions for iOS and Android.
• Review the running interface. Source inspection, a green build, a component story, or one happy-path screenshot is not UI/UX completion.
• Treat references as vocabulary, not authority. Extract applicable grammar without copying branded composition, assets, copy, or trade dress.
• Label assumptions. Do not present an expert critique as user research or an aesthetic preference as a usability fact.

1. Fix the design authority and scope

Inspect the request, repository instructions, accepted product evidence, existing UI, tokens, component library, typography, icons, content conventions, target stack, and available browser or device tooling.