frontend-ui-engineering

Builds accessible, responsive React components following design system conventions.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Avistian/nba --skill frontend-ui-engineering-avistian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-ui-engineering
Source: https://github.com/Avistian/nba/tree/main/.cursor/skills/frontend-ui-engineering
Command: npx skills add https://github.com/Avistian/nba --skill frontend-ui-engineering-avistian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated interfaces often look generic, ignore accessibility standards, and break on different screen sizes. This Skill guides the creation of production-quality user interfaces that follow real design systems, meet WCAG 2.1 AA accessibility requirements, and avoid the recognizable "AI aesthetic" of purple gradients and stock layouts. ## Core Features & Use Cases - Component Architecture Patterns: Enforces composition over configuration, colocated file structures, and separation of data fetching from presentation in React/TypeScript code. - Accessibility Enforcement: Covers keyboard navigation, ARIA labels, focus management, and meaningful empty/error states to meet WCAG 2.1 AA standards. - Design System Adherence: Guides consistent spacing scales, typography hierarchy, semantic color tokens, and responsive mobile-first layouts tested at 320px through 1440px breakpoints. - Use Case: When asked to build a task management dashboard, this Skill ensures the output uses composable Card components, skeleton loading states, keyboard-accessible controls, and the project's actual color palette instead of generic AI defaults. ## 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 build accessible React components?▼

Use semantic HTML elements like button instead of div for interactions, add aria-label to icon-only controls, and manage focus when dialogs open. Every interactive element must be keyboard accessible and testable by tabbing through the page.

How to manage state in React components?▼

Choose the simplest approach that works: useState for local UI state, lifted state for 2-3 siblings, Context for read-heavy values like theme, URL search params for shareable filters, and React Query or SWR for server data. Avoid prop drilling deeper than three levels.

What breakpoints should responsive design support?▼

Test layouts at 320px, 768px, 1024px, and 1440px widths. Design mobile-first with single-column layouts, then expand using responsive utilities like Tailwind's sm and lg prefixes for larger screens.

Why does AI-generated UI look generic?▼

Models default to purple palettes, excessive gradients, uniform rounded corners, and stock card grids regardless of context. Production-quality UI uses the project's actual design tokens, consistent spacing scales, and content-driven layouts instead.

When should I split a React component?▼

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.