What problem does it solve? Interfaces often feel sluggish or unpolished because of subtle animation mistakes: wrong easing curves, excessive durations, scale-from-zero entrances, and non-interruptible keyframes. This Skill encodes Emil Kowalski's design engineering philosophy to help you diagnose and fix these invisible details in UI code. ## Core Features & Use Cases - Animation Decision Framework: Determines whether an element should animate at all, which easing curve to use, and how long it should run based on usage frequency and purpose. - Structured UI Code Review: Produces Before/After/Why markdown tables identifying issues like transition: all, ease-in on UI elements, missing :active states, and incorrect transform-origin on popovers. - Implementation Guidance: Covers springs, clip-path animations, gesture physics (velocity-based dismissal, damping), CSS transform mastery, performance rules (GPU-only properties, WAAPI), and accessibility (prefers-reduced-motion, touch hover gating). - Use Case: Paste a dropdown component's CSS and receive a table of concrete fixes, such as replacing ease-in at 300ms with a custom cubic-bezier(0.23, 1, 0.32, 1) ease-out at 180ms. ## Quick Start Review my dropdown component's CSS and suggest animation improvements following design engineering best practices.