Agent skill · software engineering · addyosmani
frontend-ui-engineering
Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
Why this skill is useful
Provides specific patterns and best practices for building production-quality, accessible UIs that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-06. 83,053 stars on the source repository.
What this skill does
Frontend UI Engineering Overview Build production-quality user interfaces that are accessible, performant, and visually polished. The goal is UI that looks like it was built by a design-aware engineer at a top company — not like it was generated by an AI. This means real design system adherence, proper accessibility, thoughtful interaction patterns, and no generic "AI aesthetic." When to Use Building new UI components or pages Modifying existing user-facing interfaces Implementing responsive layouts Adding interactivity or state management Fixing visual or UX issues Component Architecture File Structure Colocate everything related to a component: Component Patterns Prefer composition over configuration: Keep components focused: Separate data fetching from presentation: State Management Choose the simplest approach that works: Avoid prop drilling deeper than 3 levels. If you're passing props through components that don't use them, introduce context or restructure the component tree. Design System Adherence Avoid the AI Aesthetic AI-generated UI has recognizable patterns. Avoid all of them: AI Default Why It Is a Problem Production Quality --- --- --- Purple/indigo everything Models default to visually "safe" palettes, making every app look identical Use the project's actual color palette Excessive gradients Gradients add visual noise and clash with most design systems Flat or subtle gradients matching the design system Rounded everything (rounded-2xl) Maximum rounding signals "friendly" but ignores the hierarchy of corner radii in real designs Consistent border-radius from the design system Generic hero sections Template-driven layout with no connection to the actual content or user need Content-first layouts Lorem ipsum-style copy Placeholder text hides layout problems that real content reveals (length, wrapping, overflow) Realistic placeholder content Oversized padding everywhere Equal generous padding destroys visual hierarchy and wastes screen space Consistent sp …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills addyosmani/frontend-ui-engineering