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 those invisible details in UI code. ## Core Features & Use Cases - Animation Decision Framework: Decide whether an element should animate at all based on usage frequency, then choose the right easing curve, duration, and technique (CSS transitions, springs, WAAPI, or clip-path). - Structured UI Review: Audit UI code against a checklist covering transition: all, ease-in misuse, transform-origin errors, missing press states, and Framer Motion hardware-acceleration pitfalls, output as a Before/After/Why markdown table. - Component Craft Guidance: Apply concrete patterns for buttons, popovers, tooltips, toasts, drawers, drag gestures, stagger animations, and reduced-motion accessibility. - Use Case: Paste a React dropdown component and receive a table of fixes, such as replacing ease-in with a custom cubic-bezier(0.23, 1, 0.32, 1) ease-out and shortening the duration from 400ms to 200ms. ## Quick Start Ask the assistant to review your UI component's animation code and suggest improvements based on design engineering principles.