What problem does it solve?
It prevents user-facing React UI from shipping as inaccessible, slow, inconsistent, or visibly “AI-generated,” which otherwise creates rework during reviews and bad user experiences.
Core Features & Use Cases
- Accessible UI engineering (WCAG 2.1 AA): Keyboard navigation, ARIA labeling, focus management, and meaningful empty/error states that work for real users.
- Production-grade component architecture: Colocation patterns, container/presentation separation, composition over configuration, and practical file structure guidance.
- Reliable state-management decisions: A state-management ladder that directs engineers to local, lifted, context, URL, server-state, or global state only when appropriate.
- Performance and UX quality defaults: Loading skeletons (not spinners), optimistic updates, and responsive layout guidance to avoid common regressions.
Use Case Example: When adding a “TaskList” screen, use this skill to design components, choose where state belongs, implement loading/empty/error UI, and ensure keyboard + screen-reader usability instead of leaving the page with placeholders.
Quick Start
Use the frontend-ui-engineering skill to design and implement a React/TypeScript TaskList component that follows WCAG 2.1 AA, uses the state-management ladder correctly, includes loading/empty/error states, and avoids AI-aesthetic styling patterns.