Skills by Emil Kowalski

Emil Kowalski's design engineering philosophy: when and how to animate, exact easing and duration values, springs, component polish and a fixed review format.

Builds an animation in the right order: whether it should animate at all, its purpose, the cheapest tool, properties, easing, interruption and reduced motion.

Checks motion code against ten firm standards and returns a findings table with a verdict.

Audits every animation in a codebase and writes a prioritized plan with a self-contained fix for each.

Keeps web animation within the frame budget: compositor-only properties, motion off the main thread, React state traps, will-change and a symptom table.

Apple's fluid interface principles for the web: instant response, direct manipulation, interruptible springs, momentum and rubber-banding.

A read-only sweep for places that deserve motion, filtered by how often they are seen and why, with a list of what was rejected.

Stress-tests a UI with worst-case data, such as long names, missing fields and huge counts, behind a toggle, and reports what broke.

Concrete CSS and meta fixes that make a web app feel native on phones: stuck hover, tap flash, dvh, input zoom, safe areas and overscroll.

Animation decisions for React Native and Expo: Reanimated or Animated, springs, keeping motion off the JS thread, press states and haptics.

Turns a vague description of a motion effect into its exact name, with hints on how to build it.

Builds several genuinely different versions of a UI piece behind an in-page picker so you can flip between them.