frontend-ui-engineering

Builds accessible, responsive UI components following design system standards and WCAG 2.1 AA guidelines.

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

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: Applies WCAG 2.1 AA standards including keyboard navigation, ARIA labels, focus management, and meaningful empty/error states. - Design System Adherence: Avoids the generic "AI aesthetic" by enforcing consistent spacing scales, semantic color tokens, and proper typography hierarchy. - Use Case: When building a new task management page, use this Skill to generate a responsive TaskList component with skeleton loading states, optimistic updates via React Query, keyboard-accessible controls, and mobile-first breakpoints. ## Quick Start Ask the agent 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 for interactions, add ARIA labels to icon-only controls, and manage focus when dialogs open. Verify keyboard navigation by tabbing through the page and test 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 values like theme or auth, and Zustand or Redux for complex client state shared app-wide. Use React Query or SWR for remote server data with caching.

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.

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

AI defaults to purple gradients, excessive rounding, and stock card grids that ignore real design systems. Avoid this by using the project's actual color palette, consistent spacing scale, semantic tokens, and content-first layouts.

When should I split a React component into smaller pieces?

Split components exceeding roughly 200 lines or handling multiple responsibilities. Separate data fetching containers from presentational components, and extract complex state logic into custom hooks colocated with the component.