charles-ux-animation

Installation
SKILL.md

UX & Animation

From Charles Liu's "20 Principles of UX & Animation" reel, extended with Emil Kowalski's rules for interface animation, the motion techniques in Josh Puckett's Interface Craft, and more of the laws of UX. Built on Disney's 12 principles of animation (Frank Thomas and Ollie Johnston, The Illusion of Life), Raphael Salaja's userinterface.wiki and Jon Yablonski's Laws of UX.

Every interaction answers five questions, in this order: should it move, where should the eye go, how should it move, can people find it, hit it and choose it, and can they finish. Walk them in that order every time. A later answer never rescues an earlier one: the perfect curve on an animation that shouldn't exist is still wrong.

Run it

  1. Match the stack. Find what the project already animates with (CSS transitions, Tailwind, Motion as motion or framer-motion, React Spring, WAAPI) and write in that. State changes stay in CSS transitions. If Motion is installed, use it only for what CSS can't do: animating an element out as it unmounts, layout changes, and springs that follow a finger. Never add a library for what a CSS transition does, and never hand-roll a spring where Motion is installed. Why: two systems animating the same kind of change drift apart in timing and in how they handle interruption.
  2. List the interactions in scope. For each, write down what triggers it (pointer, touch, keyboard, network, scroll), how often one person fires it, and what it has to tell them. Then cut, or in a review flag, every element and step that doesn't serve the task (Occam's razor, question 5) before polishing anything. Why: restyling something that's about to be deleted is wasted work.
  3. Walk questions 1–5 below, question by question, checking every interaction against each rule. Each subsection says when it applies; skip it when nothing in scope can trigger it (if nothing travels across the screen, skip Arcs).
  4. Name the numbers. Durations, curves and springs live in named tokens at the top of the file or in the theme, and every animation uses them. A sequence of three or more stages gets a storyboard: a comment listing when each stage starts, a TIMING object, and one config object per element (storyboards). When you can run the app, tune the values live (a dev-only control panel), then hard-code what works. Why: a number nobody can find is a number nobody tunes.
  5. Verify with the checks at the end.

Recipes with exact values for modals, drawers, popovers, tooltips, toasts, entrances, exits, expanders, icon swaps, async buttons, numbers, sliders and carousels are in references/recipes.md, with code wherever a value isn't enough. Curves, springs, interruptibility, arcs, mapping one value to another, rubber banding, loops, masks, cross-fades, storyboards, timelines and performance are in references/techniques.md. Both files open with a list of their sections; read the section a rule points to.

Reviewing instead of building? Open the report with the interaction list from step 2. Then write one table row per finding: severity, principle, where (file and line, or frame), before, after. Severity is broken (a wrong result, lost input, a blocked or skipped step), friction (slower or more confusing than it needs to be) or polish. Sort by severity, then by the five questions; a Verify finding goes under the question it serves (reduced motion and animated properties under 3). Bugs no principle covers go in a list after the table.

1. Should it move?

Installs
194
GitHub Stars
182
First Seen
7 days ago