frontend-ui-engineering

Builds accessible, responsive React components following design system and WCAG standards.

Updated May 5, 2026
One-click install
npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill frontend-ui-engineering-nikegeorgian-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-ui-engineering
Source: https://github.com/nikegeorgian-stack/otgruzka-tovara/tree/main/.cursor/skills/frontend-ui-engineering
Command: npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill frontend-ui-engineering-nikegeorgian-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated interfaces often look generic, ignore accessibility requirements, and break on different screen sizes. This Skill guides the construction of production-quality user interfaces that follow a real design system, meet WCAG 2.1 AA accessibility standards, and handle loading, error, and empty states properly. ## Core Features & Use Cases - Component Architecture Patterns: Enforces composition over configuration, colocated file structure, and separation of data fetching from presentation in React components. - Accessibility Compliance: Provides concrete patterns for keyboard navigation, ARIA labels, focus management, and meaningful empty/error states meeting WCAG 2.1 AA. - Design System Adherence: Avoids the generic "AI aesthetic" (purple gradients, excessive rounding, stock card grids) by enforcing consistent spacing scales, typography hierarchy, and semantic color tokens. - Use Case: When asked to build a task management page, the Skill produces a responsive layout with skeleton loading states, keyboard-accessible interactive elements, optimistic updates via React Query, and proper empty states instead of a generic gradient-heavy template. ## Quick Start Ask the assistant to build a responsive, accessible task list page with loading 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 that meet WCAG standards?▼

Use semantic HTML elements like button instead of div, add aria-label to icon-only controls, manage focus when dialogs open, and ensure 4.5:1 contrast for text. Test by tabbing through the page and running axe-core checks.

How to structure React components for production applications?▼

Colocate component files (implementation, tests, hooks, types) in one folder, prefer composition over configuration props, and separate data-fetching container components from presentational components. Keep components under 200 lines.

What state management approach should I use in React?▼

Choose the simplest option that fits: useState for local UI state, Context for theme or auth, URL search params for shareable filters, React Query or SWR for server data, and Zustand or Redux only for complex app-wide state.

Why does AI-generated UI look generic and how do I avoid it?▼

AI defaults to purple gradients, excessive rounding, oversized padding, and stock card grids. Avoid this by using the project's actual color palette, consistent spacing scale, semantic tokens, and content-first layouts with realistic copy.

How do I handle loading and error states in React data fetching?▼

Render skeleton placeholders instead of spinners for content areas, show retry actions on errors, and display actionable empty states. Use optimistic updates with React Query mutations to roll back changes on failure.