frontend-ui-engineering

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

Updated May 13, 2026
One-click install
npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill frontend-ui-engineering-sapatamuku-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-ui-engineering
Source: https://github.com/sapatamuku-creator/mastersapatamuku/tree/main/releases/v2.7/.agents/skills/frontend-ui-engineering
Command: npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill frontend-ui-engineering-sapatamuku-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated UI often looks generic, ignores accessibility requirements, and skips responsive design, resulting in interfaces that fail WCAG standards and feel unpolished. This Skill enforces production-grade frontend 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: Provides concrete patterns for keyboard navigation, ARIA labels, focus management, and WCAG 2.1 AA contrast requirements. - Design System Adherence: Eliminates the generic "AI aesthetic" (purple gradients, excessive rounding, stock layouts) in favor of project-specific spacing scales, semantic color tokens, and type hierarchies. - Use Case: When building a new task management page, use this Skill to generate a TaskList component with skeleton loading states, empty states, optimistic updates via React Query, keyboard-accessible controls, and responsive grid layouts tested at 320px through 1440px. ## 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 build accessible React components that meet WCAG standards?▼

Use semantic HTML elements like button instead of div, add aria-label to icon-only controls, manage focus when dialogs open, and ensure 4.5:1 contrast for normal text. Test by tabbing through the page and running axe-core checks.

How to avoid the generic AI-generated look in UI design?▼

Replace default purple palettes and heavy gradients with the project's actual color tokens, use a consistent spacing scale instead of arbitrary pixel values, and build content-first layouts rather than stock card grids. Use realistic placeholder content to reveal layout problems.

When should I use Context versus Zustand versus React Query for state?▼

Use useState for component-local UI state, Context for read-heavy values like theme or auth, URL search params for shareable filters, React Query or SWR for remote server data, and Zustand or Redux only for complex client state shared app-wide.

What breakpoints should I test for responsive design?▼

Test at 320px, 768px, 1024px, and 1440px. Design mobile-first with single-column layouts, then expand using responsive utilities like sm:grid-cols-2 and lg:grid-cols-3 as screen width increases.

Why should I use skeleton loaders instead of spinners?▼

Skeleton loaders preserve layout structure and reduce perceived loading time by previewing content shape, while spinners cause layout shift and give no context. Mark skeletons with aria-busy and an aria-label so screen readers announce the loading state.