frontend-ui-engineering

Builds accessible, responsive UI components following design system standards.

Updated May 19, 2026
One-click install
npx skills add https://github.com/LonelyTraderBay/vittrade-flutter --skill frontend-ui-engineering-lonelytraderbay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-ui-engineering
Source: https://github.com/LonelyTraderBay/vittrade-flutter/tree/main/.agents/skills/frontend-ui-engineering
Command: npx skills add https://github.com/LonelyTraderBay/vittrade-flutter --skill frontend-ui-engineering-lonelytraderbay

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 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 content and interaction patterns. ## Core Features & Use Cases - Component Architecture Guidance: Enforces composition over configuration, colocated file structures, and separation of data fetching from presentation. - Accessibility Enforcement: Covers keyboard navigation, ARIA labels, focus management, and meaningful empty/error states to meet WCAG 2.1 AA. - Design System Adherence: Avoids the generic "AI aesthetic" (purple gradients, excessive rounding, stock layouts) by applying consistent spacing scales, typography hierarchy, and semantic color tokens. - Use Case: When asked to build a task list page, the Skill produces a responsive component with skeleton loading states, optimistic updates, keyboard-accessible controls, and proper empty/error handling instead of a bare list. ## Quick Start Ask the agent to build a responsive, accessible settings page component that follows the project's design system and includes loading, error, and empty states.

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. Every interactive element must be keyboard operable and meet WCAG 2.1 AA contrast ratios of 4.5:1 for normal text.

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

Use the project's actual color palette instead of default purple gradients, apply consistent border-radius and spacing from the design system, and build content-first layouts rather than stock card grids. Replace placeholder copy with realistic content to expose layout problems.

What state management approach should I use for UI components?▼

Choose the simplest option that fits: useState for local UI state, lifted state for a few siblings, Context for theme or auth, URL search params for shareable filters, and server-state libraries like React Query for remote data. Avoid prop drilling deeper than three levels.

Does this guidance apply to responsive mobile-first design?▼

Yes, layouts are designed mobile-first and expanded with breakpoint utilities, such as single-column grids scaling to multiple columns on larger screens. Components should be tested at 320px, 768px, 1024px, and 1440px widths.

Why should I use skeleton loaders instead of spinners?▼

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