Stops AI-generated UI from defaulting to purple gradients and templated hero sections by forcing a named design direction first.
Frontend UI Engineering Skill
Addy Osmani's skill for building production-quality, accessible, responsive interfaces: component architecture, the simplest workable state, design-system adherence, a list of AI-aesthetic defaults to avoid, WCAG 2.1 AA and a verification checklist.
Install
Other ways to install
About
- Component architecture, file structure and composition patterns
- State ladder from local state to a global store, prop drilling capped at three levels
- Named list of AI-aesthetic defaults to avoid, with production alternatives
- Reference-led design contract before building a new visual direction
- WCAG 2.1 AA: keyboard navigation, ARIA, focus management, empty and error states
- Verification checklist using the project's own tooling
Frontend UI Engineering is one of the engineering-practice skills in Addy Osmani's addyosmani/agent-skills collection. The agent uses it whenever it builds or modifies user-facing UI: new components or pages, layouts, interactivity and state, or visual and UX fixes. Its stated aim is UI that looks built by a design-aware engineer rather than generated by a model.
It covers component architecture and file structure with composition patterns, and a ladder for choosing state, from local state up through lifted state, context, URL state and server-state libraries to a global store, with prop drilling capped at three levels. On design it asks the agent to adhere to the project's design system, to study two or three reference screens and write a short design contract before building a distinct visual direction, and to avoid a named list of AI defaults: purple-indigo palettes, heavy gradients, maximum rounding, generic heroes, placeholder copy, oversized padding, stock card grids and heavy shadows. Spacing, type hierarchy and semantic colour tokens with contrast ratios get their own rules.
Accessibility targets WCAG 2.1 AA with keyboard navigation, ARIA labels, focus management and meaningful empty and error states, followed by responsive design and loading and transitions. The skill closes with common rationalizations, red flags and a verification checklist (no console errors, keyboard and screen-reader checks, 320 to 1440 px breakpoints, every state handled, axe-core clean), run with the project's own tooling rather than newly installed dependencies. MIT licensed.
SKILL.md
The instructions your agent loads, as published by Addy Osmani.
Related Skills
See all Frontend UI Engineering alternativesA searchable UI/UX knowledge base as an agent skill: styles, product palettes, font pairings, 120 UX guidelines, icons, charts and 22 stacks, queried by a local Python script to generate and persist design systems.
Paul Bakaus' frontend design skill: one entry point with over 20 commands to shape, critique, audit, polish, animate and harden websites, app UI and design systems, guided by product context in PRODUCT.md and DESIGN.md.
The official shadcn/ui skill: project-aware rules and CLI workflows for adding, composing, styling and updating shadcn components, applying presets, and turning a DESIGN.md into a themed design system.