frontend-ui-engineering

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

1|Updated Jul 5, 2026
One-click install
npx skills add https://github.com/yersonargotev/packy --skill frontend-ui-engineering-yersonargotev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-ui-engineering
Source: https://github.com/yersonargotev/packy/tree/main/bundle/skills/frontend-ui-engineering
Command: npx skills add https://github.com/yersonargotev/packy --skill frontend-ui-engineering-yersonargotev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated interfaces often look generic, ignore accessibility requirements, and lack proper loading, error, and empty states. This Skill provides concrete patterns for building production-quality user interfaces that follow a project's design system, meet WCAG 2.1 AA accessibility standards, and work across screen sizes. ## 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 keyboard navigation, ARIA labeling, focus management, and contrast requirements with a detailed WCAG 2.1 AA checklist reference. - Design System Adherence: Identifies and eliminates common AI-generated UI anti-patterns such as purple gradients, excessive rounding, and stock card grids in favor of project-specific tokens and spacing scales. - Use Case: When asked to build a task management page, the Skill guides creation of a responsive grid layout with skeleton loading states, optimistic updates via React Query, keyboard-accessible controls, and meaningful empty states. ## Quick Start Ask the AI to build a responsive, accessible task list component with loading, error, and empty states using this Skill.

Frequently Asked Questions about frontend-ui-engineering

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

FAQPage Schema
When should I split a React component into smaller pieces?▼

Split components that exceed roughly 200 lines, handle both data fetching and rendering, or require prop drilling deeper than three levels. Separate container components that fetch data from presentational components that render it.