Communitygithub.com

antheo-motion

Decides whether a thing should move, then gives it exact timing, easing and distance (presses, hovers, menus, dialogs, sheets, drags, page transitions) with reduced motion handled. Use when UI feels janky, static or overdone, when a drawer or drag feels wrong, or before shipping any animation.

What is antheo-motion?

antheo-motion is a Claude Code agent skill that decides whether a thing should move, then gives it exact timing, easing and distance (presses, hovers, menus, dialogs, sheets, drags, page transitions) with reduced motion handled. Use when UI feels janky, static or overdone, when a drawer or drag feels wrong, or before shipping any animation.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/antheo-design/skills/tree/HEAD/skills/antheo-motion

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Antheo Motion

Motion is information about change: something arrived, left, moved or answered you. Motion that explains nothing is noise; a change with no motion is a jump. This skill decides which changes move and gives each its exact timing. A component's one signature moment belongs to antheo-moment; the duration tokens are generated by antheo-tokens; the reduced-motion requirement is checked by antheo-access. Auditing, cutting or planning the motion across a whole app is antheo-motion-audit's.

Decide in this order

  1. List every change the screen makes: what opens, closes, appears, leaves, reorders, updates, loads, succeeds or fails.
  2. Mark how often a person sees each: many times a day, daily, or rarely.
  3. Give each its duration and easing from the tables below.
  4. Hand the one rare, meaningful event, if there is one, to antheo-moment.
  5. Check it fast, twice, and with reduced motion, then film it and read the frames (below).

Name why it moves, or don't move it

"This moves so the person understands ___." Can't finish the sentence: no animation.

The more often it is seen, the less it moves

How oftenIt gets
Many times a day (typing, rows, tabs, menus, a palette)at most 150ms, 4px of travel; from the keyboard, nothing but a short fade
Daily (a dialog, a sheet, a toast, a save)a short arrival and a quicker exit, 150 to 300ms
Rarely (a first success, an order placed)the one place for a signature moment (antheo-moment)

The durations, by job

TokenValueTakes
--dur-instant100mscolour and opacity feedback
--dur-fast150mspress, hover in and out, a menu or tooltip opening
--dur-base200msthings leaving, a dialog closing, a value or text swap, a toast arriving
--dur-open250msa dialog opening, tabs, an accordion, a card resizing
--dur-slow300msa sheet or drawer rising, a marker sliding across
--dur-page400msa page or shared-element transition

Interface motion stays at or under 300ms; page moves at or under 400ms. Spinners, progress and scroll-linked motion run linear.

Open and close, as pairs

ThingOpensCloses
Menu, popover, select150ms, from scale(0.97) and a fade, at the trigger120ms
Tooltip400ms delay, then a 150ms fade; at once within 300ms of another closingat once
Dialog250ms: 8px rise, fade, scale from 0.96200ms
Sheet, drawer300ms from its edge, fully opaque throughout (no fade, no blur)200ms
Toast200ms, 12px rise200ms, out the way it came
Accordion, height reveal250ms, grid-template-rows: 0fr to 1fr200ms

Never delay a close or a hover-out: shorten the duration instead.

One curve for arriving and leaving

--ease-out cubic-bezier(0.23, 1, 0.32, 1) for everything that enters or leaves. --ease-in-out cubic-bezier(0.77, 0, 0.175, 1) only for something moving from one place on screen to another. --ease-in only for something thrown away for good. Exits are quicker than entrances and travel about half as far.

Small distances, never from zero

Travel 4px for a value swap or a popover, 8px for a dialog, 12px for a toast, 24px for a hero part; the full edge only for a sheet. Enter from scale(0.96) (0.97 for menus, 0.98 for tooltips) with opacity 0, never from scale(0). Blur 4px on a text or icon swap, 8px on a large surface, 2px on a crossfade under 200ms.

What may animate

transform and opacity (and colour) by default; a short filter blur, clip-path, and grid-template-rows for height reveals where needed. Never transition: all, never width, height, top, left or margin, never box-shadow itself: put a changing shadow on a pseudo-element and fade it. will-change only after a profile asks.

Grow from the trigger

Menus and popovers take their transform-origin at the trigger (Radix exposes --radix-popover-content-transform-origin); a modal stays centred; a sheet comes from the edge it lives on; a shared element (a card opening into its page) uses one view-transition-name on each side.

Transitions for state, keyframes for one-shot

Anything a person can toggle uses a CSS transition or a spring, which reverse mid-flight; keyframes only for things that play once.

Stagger 30 to 40ms, the first eight, 300ms in all

60 to 80ms for a hero's three to six parts. Never stagger something opened often, and never block a click while items arrive.

Springs only where a hand moves it

A switch knob, a released drag, a gliding segmented pill. Bounce 0 to 0.2 on controls (the overshoot stays inside the track), up to 0.45 for a rare celebration; one wobble at most. A drag follows the finger with no transition and, on release, springs from the release speed; a sheet closes on a flick faster than about 0.11px per ms, or once it has travelled min(64px, 15%) of its height, otherwise it springs back (references/gestures.md).

Nothing jumps

Every value that changes is seen to change; a removed row closes its gap; space is reserved for what appears (layout shift under 0.1). On load, at most one entrance. Switch themes with transitions off for one frame.

Reduced motion keeps the story in fades

Under prefers-reduced-motion: reduce, travel, scale, blur, parallax and bounces become a 150 to 200ms opacity crossfade; a switch knob moves at once; autoplaying loops stop. Anything that moves for more than 5 seconds by itself has a pause control (WCAG 2.2.2); nothing flashes more than 3 times a second (2.3.1).

Across a whole app

  1. Find: a table of every change, how often it is seen, how it moves now, how it should.
  2. Improve: tokens for every number, the missing exits, origin at the trigger, one pattern at a time.
  3. Remove: anything that animates on every load, plays on a many-times-a-day action, delays the next action, loops while people read, or runs over 300ms on a routine action. When unsure, remove.
  4. Approve or block: a reason sentence, tokens only, the allowed properties only, an exit quicker than the enter, reduced motion handled, watched at normal speed and at 4× CPU slowdown.

Check it

Click everything fast, twice: it reverses, never jumps. Open the menu twenty times: still quick. Throttle the CPU 4×: still smooth. Turn on reduced motion: nothing travels.

Watch it: a still can't judge motion

A screenshot of the resting state says nothing about how a thing moves, and every checker reads still frames. So film each motion you made and look at the frames before calling it done:

node <antheo-motion>/scripts/filmstrip.mjs <url> --clip ".tuner" --click ".preset" --duration 600
node <antheo-motion>/scripts/filmstrip.mjs <url> --clip ".sheet" --drag ".handle" --by 0,240 --duration 900

It slows the page to 0.1× (CSS, Web Animations and the JavaScript clock), does the one thing, and lays 12 frames of the element on one sheet, each with its time. Open the sheet and read every frame:

  • each frame looks composed on its own: no hard edge sliding through, no flash of the wrong colour, no empty box
  • every value that changes is seen to change: a number that should roll doesn't snap while its needle still travels
  • nothing reflows or jumps mid-way; the first frame already answers the press
  • the end settles where it should: a spring overshoots a little and comes back, a control doesn't stop dead
  • film it again with --reduce and --dark: the story is still told, and dark has no flash of light

Fix what a frame shows, film it again, and keep the last sheet as the evidence.

What generated UI gets wrong here

Check each in references/habits.md before calling it done: transition: all · content hidden until a script reveals it · a blanket reduced-motion reset · a focus ring that fades or slides in · motion that performs · hover effects on things that aren't clickable · a transition reading a name nobody defined.

When more motion is right

The purpose and frequency rules decide; the numbers are defaults. A game, a creative tool, a learning product or a brand moment the person asked for may move more and longer. It still answers input at once, never blocks the next action, can be interrupted mid-way, respects reduced motion, and shows its cost: a slow frame on a mid-range phone is a finding whatever the style.

Done

  • Every change listed with how often it is seen; frequent ones barely move; keyboard actions don't travel
  • Durations and easing from the tokens; the open and close pairs above; no delayed closes
  • Only the allowed properties; origin at the trigger; nothing from scale(0)
  • Reduced motion becomes a crossfade; loops over 5s can pause
  • Clicked fast twice, at 4× slowdown and with reduced motion
  • Each motion filmed (scripts/filmstrip.mjs), every frame read, light, dark and reduced
  • Checked against every habit in references/habits.md

Files

  • scripts/filmstrip.mjs: films one motion at 0.1× into a sheet of frames, with the time under each
  • references/recipes.md: the index of 36 copy-ready recipes, one file each in references/recipes/, from press and popover to number rolls and streaming text
  • references/why.md: the reason behind every rule, for when a value looks arbitrary or someone wants to break it
  • references/gestures.md: drag, swipe, sheets, snap points, momentum, rubber banding (phone feel: antheo-mobile)
  • references/choreography.md: several things as one change: closing gaps, reorders, resizing panels, crossfades
  • references/springs.md: springs in plain words, presets, a 30-line JS spring, linear() with fallbacks
  • references/performance.md: what is cheap to animate, 60fps on a cheap phone, how to profile
  • references/advanced.md: 3D, scroll-driven animation, View Transitions, filming motion
  • references/vocabulary.md: plain descriptions to pattern names to recipes
  • references/motion-kit.css: the fallback copy of the generated motion.css
  • references/habits.md: what generated UI gets wrong here, each with its fix

Related Skills