frontend-ui-engineering

Builds accessible, responsive React components following design system conventions.

Updated May 19, 2026
One-click install
npx skills add https://github.com/richardnguyen0715/agent-sharing --skill frontend-ui-engineering-richardnguyen0715
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-ui-engineering
Source: https://github.com/richardnguyen0715/agent-sharing/tree/main/.github/skills/frontend-ui-engineering
Command: npx skills add https://github.com/richardnguyen0715/agent-sharing --skill frontend-ui-engineering-richardnguyen0715

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated interfaces often look generic, ignore accessibility standards, and lack proper loading, error, and empty states. This Skill enforces production-quality UI engineering practices so components are accessible, responsive, and consistent with the project's design system. ## Core Features & Use Cases - Component Architecture Guidance: Enforces composition over configuration, colocated file structure, and separation of data fetching from presentation in React/TypeScript components. - Accessibility Compliance: Applies WCAG 2.1 AA requirements including keyboard navigation, ARIA labels, focus management, and meaningful empty/error states. - Design System Adherence: Avoids the generic "AI aesthetic" (purple gradients, excessive rounding, stock layouts) by enforcing spacing scales, semantic color tokens, and type hierarchy. - Use Case: When asked to build a task list page, the Skill produces a container/presentational component split with skeleton loading, optimistic updates via React Query, keyboard-accessible controls, and responsive grid layouts tested at 320px to 1440px breakpoints. ## Quick Start Ask the AI to build a responsive, accessible task list component with loading, error, and empty states following the project's design system.

Frequently Asked Questions about frontend-ui-engineering

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

FAQPage Schema
How do I build accessible React components?▼

Use semantic HTML elements like button instead of div, add ARIA labels to icon-only controls, manage focus when dialogs open, and ensure every interactive element works with keyboard navigation. Test by tabbing through the page and running axe-core checks.

How to structure React components for large projects?▼

Colocate each component with its tests, stories, hooks, and types in a single folder. Separate data-fetching container components from presentational components, prefer composition over configuration props, and split components exceeding 200 lines.

When should I use Context vs Zustand vs React Query for state?▼

Use useState for local UI state, Context for read-heavy values like theme or auth, URL search params for shareable filters, React Query or SWR for remote server data, and Zustand or Redux only for complex client state shared app-wide.

Why does AI-generated UI look generic?▼

Models default to purple palettes, excessive gradients, uniform rounded corners, and stock card grids regardless of context. Fix this by using the project's actual design tokens, spacing scale, and type hierarchy instead of invented values.

What breakpoints should I test for responsive design?▼

Test at 320px, 768px, 1024px, and 1440px widths. Design mobile-first with single-column layouts, then expand to multi-column grids at larger breakpoints using responsive utility classes.