Emil Kowalski Design Skills: A Guide to Motion and Interface Polish

Emil Kowalski Skills is an open collection for designers and engineers. Rather than generating one fixed visual style, it helps AI agents make better decisions about animation, interface detail, and frontend-library selection.

The repository says the skills are based on Emil Kowalski’s experience at companies including Vercel and Linear. It also makes an important point: AI amplifies domain expertise rather than replacing the need to develop it.

Why these skills matter

Interface quality is often the result of small choices: whether an entering animation uses ease-in or ease-out, whether a boundary should be a solid border or a translucent shadow, whether a transition can be interrupted, and whether a state change needs animation at all.

A general coding agent can implement motion while choosing the wrong ingredients. The Emil Kowalski collection separates different problems into focused skills, allowing an agent to load narrower guidance for the task instead of applying one enormous design prompt to every interface.

Installation

The repository currently documents:

npx skills@latest add emilkowalski/skills

Before installation, inspect the selected skills and confirm that your host supports the generated Agent Skills structure. Teams should prefer a project-level trial and review all version-control changes.

Key skills in the collection

emil-design-eng

The main skill focuses primarily on animation while also including interface-design guidance. It is useful when implementation quality, motion, and detail need to be considered together.

animate

This skill helps build an animation from scratch by selecting curves, durations, properties, and implementation details. It works best with a concrete interaction goal such as opening a dialog, reordering a list, or changing state.

review-animations

This workflow strictly reviews existing animation. It can examine whether timing feels slow, whether the curve matches entry or exit, whether animated properties are efficient, and whether several effects compete for attention.

improve-animations

This skill audits animations across a codebase and produces prioritized, self-contained plans. It is better suited to systematic cleanup than one component adjustment.

find-animation-opportunities

It identifies areas that genuinely benefit from motion while also explaining what should remain still. This guards against repetitive section reveals and decorative animation.

apple-design

The repository describes this as Apple interface and fluid-motion principles distilled from public WWDC design talks and translated for the web. It is relevant to gestures, springs, momentum, interruptible transitions, materials, and precise typography.

pick-ui-library

This skill helps an agent choose a trusted library for the task rather than hand-building a mature component or installing an abandoned package. Any recommendation still needs current checks for compatibility, maintenance, license, and bundle impact.

A practical motion workflow

Suppose you are improving a command palette:

Define what the motion communicates, such as continuity between the trigger and focused surface.
Use animate to choose properties, duration, and curve.
Implement keyboard, focus, and reduced-motion behavior.
Use review-animations to critique the result.
Test on a real device and under lower performance.

Example prompt:

Use the animate skill to improve the command palette’s entry and exit.
It must support keyboard dismissal and prefers-reduced-motion.
Do not animate the background list.
Explain the curve, duration, and property choices before changing code.

How it works with other design skills

Frontend Design can own the overall visual direction. Impeccable can own system-level critique and release checks. Emil’s focused skills can then handle motion and design-engineering details.

For example, use Frontend Design to establish a quiet, precise, low-motion direction; use an Emil skill for the critical interactions; then use Impeccable Audit for accessibility and responsive behavior. Avoid letting several skills rewrite the same rules at once.

Keep source boundaries clear

Articles about a named designer should distinguish between the author’s public statements, rules inside the repository, and third-party interpretation. Do not present community summaries as Emil Kowalski’s own claims. The descriptions above come from the public repository; any broader quotation or interpretation should link to the original source.

Conclusion

Emil Kowalski Design Skills turn “better motion” and “more polished UI” into concrete choices about timing, curves, properties, opportunities, review, and tooling. They are most useful for teams with a functioning interface that want to improve interaction quality and design engineering.

Continue with Frontend Design vs Emil Kowalski Design Skill or browse the complete design skill directory.