ui-ux-architect

Standardize accessible React/Next.js UI design with WCAG 2.2 AA compliance.

3|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/ralvarezdev/ralvaskills --skill ui-ux-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-ux-architect
Source: https://github.com/ralvarezdev/ralvaskills/tree/main/skills/frontend/ui-ux-architect
Command: npx skills add https://github.com/ralvarezdev/ralvaskills --skill ui-ux-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a unified set of UI/UX standards to ensure accessible, consistent frontend design across teams, reducing rework and enabling rapid, safe component development.

Core Features & Use Cases

  • Accessibility floor: WCAG 2.2 AA compliance for all shipped components.
  • Component primitives: Radix + Tailwind + shadcn/ui as a minimal, adaptable foundation.
  • Design tokens: semantic, color-OKLCH based theming with dark mode support.
  • Responsive patterns: mobile-first layout with container queries for adaptive UI.
  • Four-state surfaces: loading, error, empty, and success states for all async operations.
  • Forms, motion, icons, and i18n: accessible, labeled controls, motion respects user preferences, consistent iconography, and potential internationalization scaffolding.

Quick Start

Audit a new component library against WCAG 2.2 AA, adopt token-based theming from the design system, and implement the four-state async surfaces in all components.

Frequently Asked Questions about ui-ux-architect

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

FAQPage Schema
How do I enforce WCAG 2.2 AA compliance in a React component library?

Design tokens provide semantic, color-OKLCH based theming with dark mode support for scalable frontend interfaces. By adopting token-based theming from your design system, you ensure consistent visual language across all components and responsive layouts.

What's the best way to handle loading, error, empty, and success states in Next.js interfaces?

The best way to handle async states in Next.js interfaces is implementing four-state surfaces for all async operations. This pattern standardizes loading, error, empty, and success states across components, ensuring consistent user experiences during data fetching and interactions.

Can I use Tailwind 4 and shadcn/ui together for accessible mobile-first layouts?

Yes, you can use Tailwind 4 and shadcn/ui together for accessible mobile-first layouts. This combination serves as a minimal, adaptable foundation that supports container queries for adaptive UI, accessible labeled form controls, and motion that respects user preferences.

How do I audit an existing component library against accessibility standards?

To audit an existing component library against accessibility standards, evaluate it against WCAG 2.2 AA requirements using CI checks for contrast and keyboard accessibility. This process identifies compliance gaps and standardizes token-based theming, four-state async surfaces, and accessible controls.

Does Radix UI support internationalization and consistent iconography for design systems?

Radix UI supports internationalization scaffolding and consistent iconography when combined with shadcn/ui primitives. This setup ensures accessible, labeled controls and potential internationalization structures that scale across modern React and Next.js design systems.