frontend-ui-engineering

Guide accessible, responsive frontend component design and state management.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill frontend-ui-engineering-d0whc3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-ui-engineering
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.agents/skills/frontend-ui-engineering
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill frontend-ui-engineering-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents production UI from looking generic or broken by enforcing design-system consistency, accessibility, responsive layout discipline, and reliable state handling.

Core Features & Use Cases

  • Production-quality UI construction: Build components that look intentional and match the project’s visual system instead of an “AI aesthetic.”
  • Accessible interaction by default: Ensure keyboard navigation, correct ARIA labeling, focus management, and meaningful empty/loading/error states.
  • Practical front-end architecture: Choose appropriate state management patterns, split data fetching from presentation, and apply responsive layouts and testable loading/transition behaviors.
  • Use case: When a team is shipping a new settings page, this guidance helps implement responsive components with proper empty/error states and keyboard-friendly controls so QA and users don’t hit UX regressions.

Quick Start

Ask for a refactor plan and component implementation changes for a UI feature you’re building so it becomes accessible, responsive, and consistent with the 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 frontend components with proper keyboard and ARIA support?

Build accessible frontend components by enforcing keyboard navigation, correct ARIA labeling, and focus management. This ensures user-facing interfaces have deterministic rendering and polished UX without generic AI aesthetics.

What is the best way to handle loading, error, and empty states in responsive design?

Handle loading, error, and empty states in responsive design by applying robust state management patterns and splitting data fetching from presentation. This prevents broken production UI and ensures reliable interactive flows.

How do I make my UI design system consistent across different layouts?

Make your UI design system consistent by matching typography, color, and spacing rules across components. This approach enforces design-system adherence and prevents user interface regressions during QA testing.

Can I refactor an existing settings page to add accessible and responsive interactive flows?

Refactor an existing settings page to add accessible and responsive interactive flows by requesting a component implementation plan. This updates the UI with keyboard-friendly controls and proper empty or error states.

Why does my production UI look broken and lack design-system consistency?

Production UI looks broken when it lacks design-system consistency, responsive layout discipline, and reliable state handling. Applying structured frontend engineering ensures components appear intentional and match the visual system.

Do I need specific state management patterns for frontend UI engineering?

You need appropriate state management patterns for frontend UI engineering to split data fetching from presentation. This ensures testable loading and transition behaviors for user-facing interfaces.