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 help you diagnose and fix those invisible details in UI code. ## Core Features & Use Cases - Animation Decision Framework: Decide whether an element should animate at all, which easing curve to use, and how long it should run based on interaction frequency and purpose. - Structured UI Code Review: Get Before/After/Why markdown tables that pinpoint issues like transition: all, scale(0) entries, ease-in on UI elements, and missing :active press states. - Concrete Implementation Patterns: Apply ready-made techniques for springs, clip-path reveals, gesture velocity dismissal, staggered entrances, @starting-style entry animations, and reduced-motion accessibility. - Use Case: Paste a dropdown or modal component and receive a table of fixes, such as replacing a 400ms ease-in transition with a 200ms custom ease-out curve and an origin-aware popover scale. ## Quick Start Ask the assistant to review your button, popover, or drawer component's CSS and animation code for polish and responsiveness issues.
