uiux
UI/UX - design system, accessibility. Use when building interfaces.
When & Why to Use This Skill
This Claude skill serves as a comprehensive UI/UX framework and design system auditor, specifically optimized for modern web development. It enforces high-standard interface building by mandating the use of Radix UI and Tailwind CSS within Next.js environments. By prioritizing WCAG 2.1 AA accessibility compliance, mobile-first responsiveness, and robust state management (loading/error), this skill helps developers and designers eliminate user friction, improve conversion rates, and maintain a polished, professional brand identity across all digital touchpoints.
Use Cases
- Case 1: Building WCAG 2.1 AA compliant web interfaces to ensure full accessibility for keyboard and screen reader users.
- Case 2: Implementing a consistent design system using Radix UI primitives to avoid redundant custom code and technical debt.
- Case 3: Developing mobile-first responsive layouts with optimized touch targets (minimum 44x44px) for enhanced mobile usability.
- Case 4: Standardizing asynchronous UI operations by implementing mandatory loading states and actionable error feedback to improve user trust.
- Case 5: Auditing existing UI components to identify and resolve layout shifts or inconsistent design patterns that cause user frustration.
| name | uiux |
|---|---|
| description | UI/UX - design system, accessibility. Use when building interfaces. |
UI/UX Guideline
Tech Stack
- Framework: Next.js (with Turbopack)
- Components: Radix UI (mandatory)
- Styling: Tailwind CSS
- Icons: @iconify-icon/react
Radix UI (Mandatory)
If Radix has a primitive for it, you MUST use it. No exceptions. No custom implementations. Any custom implementation of something Radix already provides is a bug.
Non-Negotiables
- WCAG 2.1 AA compliance (keyboard navigation, screen readers, contrast)
- Touch targets minimum 44x44px on mobile
- Responsive design (mobile-first)
- Loading states for all async operations
- Error states must be actionable
- No layout shift on content load
Context
UI/UX is about removing friction between users and value. Bad UX doesn't just feel bad — it costs conversion, retention, and trust.
Driving Questions
- Where do users get confused or frustrated?
- What would a first-time user struggle with?
- Where are loading states missing or unhelpful?
- What accessibility issues exist?
- Where does the UI feel inconsistent?
- What would make the product feel more polished?