Frontend UI Engineering guides an agent when it builds or changes user-facing interfaces. It covers component file structure, composition, separating data fetching from presentation, a state management ladder and design system adherence.
The skill lists the visual habits that make generated UI look generic, sets WCAG 2.1 AA requirements for keyboard use, labels and focus, and requires loading, empty and error states and testing at four breakpoints.
What You Get
- Component architecture patterns with React examples
- A table that maps common AI-generated UI defaults to production-quality choices
- WCAG 2.1 AA guidance for keyboard, ARIA labels, focus and empty states
- A verification checklist and red flags such as components over 200 lines
Common Use Cases
- Building new components or pages
- Making an interface responsive
- Fixing accessibility and keyboard issues in a UI
- Choosing where state should live
What Makes It Unique
The skill names the visual tells of generated UI and replaces each with an instruction to use the project’s own palette, radii and spacing scale. It also describes reference-led design, which turns observed screens into a design contract and forbids copying another product’s branding or layout.
Under The Hood
The skill is a single SKILL.md of instructions with React, TypeScript, CSS and Tailwind examples. It runs no scripts and installs nothing. The agent is told to run the project’s own test, type check and lint commands and to report which checks it could not run.