ui-ux-design

Audit UI patterns and implement accessible shadcn/ui changes with Tailwind tokens.

1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/mgkyawzayya/claude-code-usage-flow --skill ui-ux-design-mgkyawzayya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-ux-design
Source: https://github.com/mgkyawzayya/claude-code-usage-flow/tree/main/.claude/skills/ui-ux-design
Command: npx skills add https://github.com/mgkyawzayya/claude-code-usage-flow --skill ui-ux-design-mgkyawzayya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI/UX changes may devolve into inconsistent visuals. This Skill enforces design consistency, accessibility, and token usage across the app.

Core Features & Use Cases

  • Component map adherence: Reuse shadcn/ui components to maintain consistency.
  • Token-driven styling: Apply Tailwind tokens for color, spacing, and typography.
  • Accessibility: Ensure keyboard nav, labels, contrast, and responsive behavior.

Quick Start

Audit the current UI and adjust a form to use Button, Input, and Dialog components with proper labels and contrast while avoiding custom CSS.

Frequently Asked Questions about ui-ux-design

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

FAQPage Schema
How do I implement accessible UI components in React with Tailwind?

Accessible UI implementation in React with Tailwind involves using pre-built shadcn/ui components, applying design tokens for consistent styling, and ensuring keyboard navigation, proper labels, and sufficient color contrast. This Skill audits your patterns and systematically updates forms, modals, and interactive controls to meet accessibility standards without custom CSS.

How can I ensure my UI stays consistent across the app?

UI consistency across apps is maintained by reusing shadcn/ui components and applying Tailwind tokens uniformly for color, spacing, and typography. This Skill maps your existing patterns, identifies inconsistencies, and updates your codebase to enforce token-driven styling so all components follow the same design system.

Can I use shadcn/ui components with Tailwind tokens for responsive design?

Yes. shadcn/ui components integrate fully with Tailwind tokens and support responsive behavior testing. This Skill validates that your forms, modals, and controls adapt correctly to mobile and desktop viewports while maintaining accessibility standards across all screen sizes.

What should I audit before redesigning forms and interactive controls?

Before redesigning forms and controls, audit the current UI patterns, component usage, token application, and accessibility gaps—keyboard navigation, labels, contrast, and responsive behavior. This Skill performs that discovery, maps components to shadcn/ui equivalents, and identifies which patterns need loading and error states.

Why avoid custom CSS when using shadcn/ui and Tailwind?

Custom CSS breaks design consistency, complicates maintenance, and often introduces accessibility issues. By using shadcn/ui components and Tailwind tokens exclusively, you ensure all styling adheres to the design system, remains maintainable, and meets accessibility requirements without conflicts or overrides.

How do I validate accessibility across forms and modals?

Accessibility validation checks keyboard navigation, ARIA labels, color contrast, and responsive behavior in interactive components. This Skill systematically tests your forms and modals against these standards and implements corrections using shadcn/ui components and Tailwind tokens to ensure compliance.