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: Determines whether an element should animate at all, which easing curve to use, and how fast it should run based on interaction 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. - Component & Gesture Guidance: Covers springs, clip-path animations, drag momentum, damping at boundaries, hardware acceleration, and reduced-motion accessibility. - Use Case: Paste a dropdown or toast component's CSS and receive a table of concrete fixes, such as replacing a 400ms ease-in transition with a 200ms custom ease-out curve. ## Quick Start Ask the assistant to review your UI animation code, for example: review this modal's CSS transitions and suggest improvements based on design engineering principles.