frontend-ui-engineering

Enforce design system compliance and WCAG 2.1 AA accessibility in frontend UI development.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/j-cogburn/d3 --skill frontend-ui-engineering-j-cogburn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-ui-engineering
Source: https://github.com/j-cogburn/d3/tree/main/tests/project-t01/.d3/skills/frontend-ui-engineering
Command: npx skills add https://github.com/j-cogburn/d3 --skill frontend-ui-engineering-j-cogburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the pervasive issue of AI-generated user interfaces that feature generic, unpolished "AI aesthetics", lack proper accessibility, fail to adhere to project design systems, and require extensive rework to meet production quality standards.

Core Features & Use Cases

  • Design System Compliance: Enforces consistent use of project-specific color palettes, spacing scales, typography, and component patterns to eliminate common AI-generated UI defaults like overused purple gradients, excessive border rounding, and generic hero sections.
  • Accessible & Responsive Implementation: Provides guidance for building keyboard-navigable, screen-reader-friendly components with proper ARIA labels, focus management, and mobile-first responsive layouts that function across all standard breakpoints.
  • Production-Grade Engineering Patterns: Covers best practices for component composition, state management, loading/error/empty states, and performance optimization to ensure UIs are fast, reliable, and user-friendly.
  • Real-World Use Case: For example, use this Skill to build a task management dashboard that matches your company's existing design system, works seamlessly on mobile devices, and passes accessibility audits without additional rework.

Quick Start

Use the frontend-ui-engineering skill to build a responsive, accessible task list component that adheres to your project's design system and includes proper 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 web components that pass WCAG 2.1 AA compliance?

To build accessible web components that pass WCAG 2.1 AA compliance, enforce production-grade standards for ARIA labels, keyboard navigation, and focus management, ensuring interfaces are screen-reader friendly and fully navigable.

Why does AI generated UI look generic and how can I enforce design system consistency?

AI generated UI looks generic because it relies on default aesthetics like purple gradients and excessive border rounding. Enforce design system consistency by applying project-specific color palettes, spacing scales, and typography to eliminate these unpolished defaults.

What is the best way to implement responsive design and loading states for frontend development?

The best way to implement responsive design and loading states for frontend development is using mobile-first layouts across standard breakpoints alongside production-grade engineering patterns for component composition, state management, and error handling.

Does this approach to UI engineering support existing interface modification and UX issue resolution?

Yes, this UI engineering approach supports existing interface modification and UX issue resolution by applying human-centered interaction patterns and performant rendering standards to resolve issues and refine current web application interfaces.

Can I use standard component architecture to avoid unpolished AI aesthetics in production UIs?

Yes, you can use standard component architecture to avoid unpolished AI aesthetics in production UIs by enforcing consistent component composition and design system patterns that ensure interfaces look human-designed rather than AI-generated.