ux-designer

Guide UI/UX design decisions with WCAG 2.1 AA accessibility and responsive patterns.

Updated Oct 26, 2025
One-click install
npx skills add https://github.com/Hieubkav/wincellarCloneBackend --skill ux-designer-hieubkav
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-designer
Source: https://github.com/Hieubkav/wincellarCloneBackend/tree/main/.claude/skills/fullstack/ux-designer
Command: npx skills add https://github.com/Hieubkav/wincellarCloneBackend --skill ux-designer-hieubkav

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design accessible, user-centered interfaces with WCAG 2.1 AA compliance, collaboration, and modern design patterns.

Core Features & Use Cases

  • Collaborative design decisions: ALWAYS ask before making design choices.
  • Accessibility by default: WCAG 2.1 AA compliance, keyboard navigation, and color contrast.
  • Modern patterns: shadcn/ui, Tailwind CSS, and React patterns for premium UI without generic aesthetics.
  • Responsive design guidance: mobile-first patterns and breakpoint-aware layouts.
  • Documentation-driven process: guidance and templates to align design decisions with brand.

Quick Start

Describe your design goals and constraints, then ask for 2–3 alternative directions with trade-offs. Review options and approve a direction before implementing.

Frequently Asked Questions about ux-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure my UI design meets WCAG 2.1 AA accessibility standards?

WCAG 2.1 AA compliance requires keyboard navigation, sufficient color contrast, and semantic HTML structure. This Skill guides you through accessibility-by-default decisions for color, typography, layout, and responsive design, applying explicit WCAG 2.1 AA criteria to each choice before implementation.

What's the best way to design responsive layouts with Tailwind CSS?

Responsive design with Tailwind CSS starts with mobile-first patterns and breakpoint-aware layouts. This Skill provides guidance on progressive disclosure, layout decisions across screen sizes, and modern responsive patterns aligned with Tailwind's utility-first approach and shadcn/ui component patterns.

How do I reduce design decision paralysis when starting a UI project?

Design decision paralysis resolves by exploring 2–3 alternative directions with documented trade-offs before committing to one approach. This Skill asks for explicit approval on each decision—color, typography, layout, and accessibility—and provides collaborative templates to align choices with your project constraints.

Can I use shadcn/ui and Tailwind CSS together for accessible component design?

Yes. shadcn/ui components with Tailwind CSS create premium, accessible UI without generic aesthetics. This Skill combines modern patterns from both frameworks, ensuring keyboard navigation, color contrast, and WCAG 2.1 AA compliance across your component system.

What accessibility considerations matter most for color and typography choices?

Color contrast and typography legibility directly impact WCAG 2.1 AA compliance. This Skill evaluates both for accessibility, ensuring sufficient contrast ratios, readable font sizes, and clear visual hierarchy while maintaining your design's visual intent and flat minimalist aesthetic.

Do I need design documentation before using this Skill?

No initial documentation is required. Start by describing your design goals and constraints, then request 2–3 alternative directions with trade-offs. This Skill guides you through documentation-driven decisions, creating alignment templates that evolve as your design choices solidify.