kinetics-uilisted
Install: claude install-skill soewaiyanag/kinetics-ui
# Kinetics UI: Web UI Animation Decisions
Use this to decide **whether** to animate, **which** pattern to use, and **what values** to apply. Go through the steps in order.
## Step 1: Should this animate at all?
Frequency of use decides how much motion to add.
| How often the user sees it | Motion budget |
|---|---|
| Constantly (typing, tab switch, hover on list rows, keyboard nav, command palette) | None or near-instant (0–100ms, opacity only) |
| Often (dropdowns, popovers, toggles, button presses) | Snappy and subtle, 150–250ms, no bounce |
| Occasionally (modals, page/route transitions, drawers) | Up to ~300ms, can use staging and stagger |
| Rarely / milestone (success, onboarding, empty→first item, payment done) | Room for flourish: pulse, sparkle, follow-through |
Hard rules:
- Feedback must start within **100ms** of input. The full response must land within **400ms** (Doherty threshold). If work takes longer, show a skeleton or optimistic state immediately.
- Never add bounce or underdamped springs to everyday UI.
- Always respect `prefers-reduced-motion`: replace movement and scale with an opacity fade or no animation.
## Step 2: Classify the motion, then use its recipe
### A. Element entering (appears on screen)
- Easing: **ease-out** (fast start, gentle landing). `cubic-bezier(0.16, 1, 0.3, 1)` or `cubic-bezier(0.22, 1, 0.36, 1)`.
- Duration: 150–250ms (small) / up to 300ms (large panels).
- Never animate from `scale(0)`. Start at **`scale(0.95)` + `opacity: