Best agent skills for interface design and prototyping
Improve interface taste, compare divergent component directions, and choose proven UI building blocks.
How to choose
Use Emil Design Engineering as the taste layer, Prototype when the right direction is still unknown, and Pick UI Library only when explicitly invoked for a dependency choice. This sequence separates visual judgment, exploration, and implementation infrastructure.
Emil Design Engineering
Encodes Emil’s core taste for polished interfaces, restrained motion, component details, and design decisions that compound.
Our take: Emil Design Engineering is the broad taste layer behind the collection. Its value lies in turning invisible interface quality into concrete choices—subtle borders, shadows, typography, component behavior, and restrained motion—without pretending polish comes from a single visual style.
Prototype
Builds genuinely different UI variants behind a visual picker so design direction can be compared in context.
Our take: Prototype addresses a common agent failure: converging on the first plausible UI and presenting cosmetic variants as exploration. By requiring materially different directions in a live picker, it turns subjective design choice into a fast comparison rather than a long prompt negotiation.
Pick UI Library
Chooses a trusted frontend library for a concrete UI need from an opinionated, maintained shortlist.
Apple Design
Applies Apple-inspired principles for physical, interruptible motion, gestures, spatial continuity, materials, and typography on the web.