What problem does it solve? Interfaces often feel sluggish or unpolished because of subtle animation mistakes: wrong easing curves, excessive durations, non-interruptible keyframes, and transforms that ignore real-world physics. This Skill encodes Emil Kowalski's design engineering philosophy to catch and fix those invisible details. ## Core Features & Use Cases - UI Code Review: Audits CSS and component code against a structured checklist (transition: all, scale(0) entries, ease-in misuse, missing transform-origin) and returns findings in a required Before/After/Why markdown table. - Animation Decision Framework: Decides whether an element should animate at all, which easing curve to use, and how long it should run based on interaction frequency and purpose. - Implementation Guidance: Covers springs, clip-path reveals, gesture velocity thresholds, GPU-safe transform/opacity animation, prefers-reduced-motion, and Framer Motion hardware-acceleration pitfalls. - Use Case: Paste a dropdown or toast component and receive a table of concrete fixes, such as replacing transition: all 300ms with transition: transform 200ms ease-out and anchoring popover scale to its trigger. ## Quick Start Ask the assistant to review your UI component's animation code and suggest improvements based on design engineering principles.