frontend-ui-engineering

Builds accessible, responsive, production-quality user interfaces following design system standards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated interfaces often look generic, ignore accessibility requirements, and break on different screen sizes. This Skill provides a rigorous engineering protocol for building user-facing UI that meets WCAG 2.1 AA standards, respects the project's design system, and avoids the recognizable "AI aesthetic" of purple gradients and stock card grids. ## Core Features & Use Cases - Component Architecture Guidance: Enforces composition over configuration, colocated file structures, and separation of data fetching from presentation in React/TSX components. - Accessibility Compliance: Covers keyboard navigation, ARIA labels, focus management, and meaningful empty/error states to meet WCAG 2.1 AA requirements. - Responsive & State Patterns: Provides mobile-first responsive layout patterns and a decision framework for choosing between local state, context, URL state, and server state. - Use Case: When asked to build a task management dashboard, the Skill guides the agent to produce a component with skeleton loading states, optimistic updates, keyboard-accessible controls, semantic color tokens, and layouts tested at 320px through 1440px breakpoints. ## Quick Start Build a responsive, accessible task list component with loading, error, and empty states that follows our 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 make React components accessible for WCAG compliance?▼

Make every interactive element keyboard accessible using native elements like button instead of div, add ARIA labels to icon-only controls, manage focus when dialogs open, and never rely on color alone to convey state. Test by tabbing through the page and running axe-core checks.

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

Use useState for component-specific UI state, lifted state for 2-3 siblings, Context for read-heavy values like theme or auth, URL search params for shareable filters, React Query or SWR for remote data, and a global store like Zustand only for complex app-wide client state.

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

AI-generated UI defaults to purple palettes, excessive gradients, uniform card grids, and oversized padding. Avoid this by using the project's actual color palette and spacing scale, semantic design tokens, content-first layouts, and realistic placeholder content instead of lorem ipsum.

What breakpoints should I test for responsive design?▼

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

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

Split components exceeding roughly 200 lines, and separate data fetching containers from presentational components. Avoid prop drilling deeper than three levels by introducing context or restructuring the component tree.