frontend-ui-engineering

Builds accessible, responsive UI components following design system standards.

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

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 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 structures, and separation of data fetching from presentation. - Accessibility Compliance (WCAG 2.1 AA): Provides concrete patterns for keyboard navigation, ARIA labels, focus management, and meaningful empty/error states. - Design System Adherence: Helps avoid the generic "AI aesthetic" (purple gradients, excessive rounding, stock card grids) by enforcing spacing scales, typography hierarchy, and semantic color tokens. - Use Case: When building a new task list page, use this Skill to generate a responsive component with skeleton loading states, optimistic updates, keyboard-accessible controls, and proper empty states instead of a bare list. ## Quick Start Use the frontend-ui-engineering skill to build a responsive, accessible task list component with loading and empty states.

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-label to icon-only controls, associate labels with form inputs via htmlFor, and manage focus when dialogs open. Verify by tabbing through the page and testing with a screen reader.

How to choose between useState, Context, and Zustand for state management?▼

Use useState for component-local UI state, Context for read-heavy shared values like theme or auth, and Zustand or Redux only for complex client state shared app-wide. Avoid prop drilling deeper than three levels by introducing context or restructuring the tree.

What breakpoints should I test for responsive design?▼

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

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

AI defaults to purple gradients, excessive border radius, uniform card grids, and oversized padding. Fix this by using the project's actual color palette, consistent spacing scale, semantic tokens, and content-first layouts instead of template patterns.

Should I use skeleton loaders or spinners for loading states?▼

Use skeleton loaders for content areas because they preserve layout and set expectations about incoming content structure. Combine them with aria-busy and aria-label attributes so assistive technologies announce the loading state.