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 issues 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. - UI Code Review with Before/After Tables: Get structured markdown table reviews covering transitions, transform-origin, spring configs, clip-path patterns, and gesture handling. - Component Polish Patterns: Apply concrete CSS and Framer Motion recipes for buttons, popovers, tooltips, toasts, drawers, and drag interactions, including performance and accessibility rules. - Use Case: Paste a dropdown component with transition: all 300ms ease-in and receive a table of fixes: exact property transitions, ease-out custom curves, origin-aware scaling, and sub-300ms durations. ## Quick Start Ask the assistant to review your UI component's animation code and suggest improvements based on design engineering principles.