What problem does it solve? Interfaces often feel sluggish or unpolished because of subtle animation mistakes like ease-in curves, scale(0) entrances, or transitions over 300ms. This Skill encodes Emil Kowalski's design engineering philosophy to help you identify 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 fast it should run based on usage frequency and purpose. - Structured UI Code Review: Produces Before/After/Why markdown tables covering transitions, transform-origin, spring configuration, clip-path usage, and gesture handling. - Performance and Accessibility Rules: Enforces GPU-friendly transform/opacity animations, hardware acceleration in Framer Motion, prefers-reduced-motion support, and hover media queries for touch devices. - Use Case: Paste a dropdown or modal component and receive a table of concrete fixes, such as replacing transition: all 300ms with transition: transform 200ms ease-out and setting popover transform-origin to its trigger. ## Quick Start Ask the assistant to review your UI component's animation code and list the issues with before and after fixes.