frontend-ui-engineering

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

1|Updated Mar 2, 2025
One-click install
npx skills add https://github.com/marjorg/setup --skill frontend-ui-engineering-marjorg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-ui-engineering
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/frontend-ui-engineering
Command: npx skills add https://github.com/marjorg/setup --skill frontend-ui-engineering-marjorg

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 project's actual design system, meet WCAG 2.1 AA accessibility standards, and handle real-world states like loading, errors, and empty content. ## Core Features & Use Cases - Component Architecture Guidance: Enforces composition over configuration, colocated file structures, 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 that meet WCAG 2.1 AA. - Design System Adherence: Helps avoid 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, optimistic updates via React Query, keyboard-accessible controls, and proper empty states instead of a bare list. ## 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
How do I make React components keyboard accessible?▼

Use native interactive elements like <button> instead of <div> with onClick, since they are focusable by default. If a custom element is unavoidable, add role="button", tabIndex={0}, and handle Enter and Space key events explicitly.

How to structure React components for large applications?▼

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

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 for server data with caching, and Zustand or Redux only for complex app-wide client state.

What contrast ratio does WCAG 2.1 AA require for text?▼

WCAG 2.1 AA requires a 4.5:1 contrast ratio for normal text and 3:1 for large text. Never rely on color alone to convey state; pair it with icons, text, or patterns.

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

AI defaults to purple gradients, excessive border radius, uniform card grids, and oversized padding. Avoid this by using the project's actual color palette, spacing scale, typography hierarchy, and content-first layouts.

What breakpoints should I test for responsive design?▼

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