frontend-ui-engineering

Create React UI components with design-system and accessibility compliance.

15|3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/LazyIsEfficient/agentic-os --skill frontend-ui-engineering-lazyisefficient
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-ui-engineering
Source: https://github.com/LazyIsEfficient/agentic-os/tree/main/.claude/skills/frontend-ui-engineering
Command: npx skills add https://github.com/LazyIsEfficient/agentic-os --skill frontend-ui-engineering-lazyisefficient

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Build production-quality user interfaces that are accessible, performant, and visually polished, aligned with a design system.

Core Features & Use Cases

  • Colocate component files (implementation, tests, stories, hooks) in a single directory for maintainability.
  • Follow a design-system-first approach with proper spacing, typography, color tokens, and responsive patterns; ensure universal accessibility (keyboard navigation, focus management) and robust loading, error, and empty states.
  • Use across dashboards, marketing pages, admin panels, and forms to deliver production-ready UI that scales with teams and product needs.

Quick Start

Create a production-ready React UI component within a single directory following the design system and accessibility guidelines.

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 production-ready React UI components that follow a design system?

Production-ready React UI components require colocating implementation, tests, stories, and hooks in a single directory. This structure enforces design-system constraints, applying proper spacing, typography, and color tokens to ensure maintainability and visual consistency across team projects.

What are the accessibility requirements for responsive frontend UI components?

Accessible responsive frontend UI components must support keyboard navigation and proper focus management. They enforce universal accessibility patterns alongside robust loading, error, and empty states to ensure interactive widgets and forms remain fully usable across dashboards and marketing pages.

How do I structure React component files for better maintainability?

Structure React component files by colocating implementation, tests, stories, and hooks within a single dedicated directory. This colocation strategy improves project maintainability and ensures production-ready UI components scale effectively alongside growing team and product requirements.

Can I use this approach for dashboards and marketing pages?

Yes, this approach applies directly to dashboards, marketing pages, admin panels, and forms. It delivers production-ready UI that adheres to design-system constraints, accessibility standards, and performance targets, scaling seamlessly across diverse team projects and product needs.

Why do my UI components need loading, error, and empty states?

UI components require loading, error, and empty states to handle data fetching and edge cases robustly. Enforcing these universal states ensures interactive widgets and forms maintain visual polish and functional reliability within a production design system.