# Build Animation

> Motion rules are in the UI taste section of ~/agent-skills/working-agreements/AGENTS.md: one

- Skill: `amsborse/build-animation` (Agent Skill, multi-file: 13 files)
- Install (CLI): `npx get-skill add amsborse/build-animation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/amsborse/build-animation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: amsborse (https://skillmd.com/u/amsborse)
- Updated: 2026-11-17
- Page: https://skillmd.com/skills/amsborse/build-animation

---


# Build animation

Motion rules are in the UI taste section of `~/agent-skills/working-agreements/AGENTS.md`: one
synchronized movement, things travel to their new place, no snaps or visible loop restarts, no
gimmicks, and every animation communicates something.

The feel is the same whatever the style: slow scroll, a single signature living visual, travel
instead of snaps, and still-first heavy visuals. The material and motion character come from a
style add-on in `~/agent-skills/styles/`: `cinematic.md` (weighted camera, plates),
`claymorphism.md` (springs with squash and give) and `glassmorphism.md` (a drifting field
under frosted depth). Read the project's chosen add-on first. If none has been chosen, use the
one the user names, or stay neutral.

Choose technology with `~/agent-skills/shared/creative/selector.md` (CSS and native APIs
first, one engine per project) and techniques from `~/agent-skills/shared/creative/README.md`,
loading only the files you use (scroll choreography, kinetic typography, media reveals,
shared-element and scene transitions, parallax). Motion intensity follows the product
(`~/agent-skills/shared/creative/adaptation.md`).

Before building a component, interaction or effect, search Arsenal and reuse what fits; register
what you build there (`~/agent-skills/shared/creative/arsenal.md`). Extra selectable designs
follow `~/agent-skills/shared/creative/design-variants.md`.

## Pick the path

- **Micro-interaction or transition:** use the project's motion library or CSS. Animate transform
  and opacity only, 150–400 ms, with an ease-out curve and a `prefers-reduced-motion` fallback.
  Motion and hover never shift layout or change an element's size or position. (high) Motion
  never delays critical actions or content, does not replay on small scrolls and never hijacks
  scrolling. (high)
- **Hover affordance on tiles or cards:** follow `workflows/hover-affordance.md` (hover glow and
  elevation, lift, underline grow, arrow nudge, stretched link, focus parity, reduced motion).
- **Signature visual or hero effect:** one living element blended into the page with masks, not
  boxed. Canvas or WebGL in a single pass, with a devicePixelRatio cap, paused by
  IntersectionObserver and `visibilitychange`.
- **Cinematic landing page:** build the page with `build-ui`, then choreograph it here with the
  `cinematic.md` add-on, `shared/creative/techniques/scroll-choreography.md` and
  `shared/creative/techniques/kinetic-typography.md`.
- **Reference image of a cinematic scene:** follow `workflows/cinematic-plate/cinematic-plate.md`
  (a generated text-free plate plus live layers; templates and scripts are in that folder).
- **Long chaptered page:** use the chapter rail and slow scroll in `workflows/chapter-rail.md`
  (a dot rail of in-page links with a spring-filled line, plus Lenis). The owner likes this pattern.
- **WebGL or canvas hero that must stay fast:** follow `workflows/heavy-hero-performance.md`. It
  covers the frame governor, rendering a still plate first and upgrading after input or idle, and
  preloading the largest image.
- **Isolated heavy effect:** delegate the implementation to Codex (UI work, per
  `~/agent-skills/shared/agent-routing.md`) with the `coordinate-agents` skill, then review it yourself.
- **Motion audit:** record or screenshot the states, then list snaps, jank, competing motions and
  missing reduced-motion handling, each with a fix.

## Verify

Follow `~/agent-skills/shared/creative/visual-loop.md` and run the `audit-design` runner (it
measures offscreen and idle rendering, long frames and reduced motion). Check in the running app: frames at the start, middle and end, both themes, and reduced motion on.
Measure frame time with a Performance trace or `requestAnimationFrame` deltas. For heavy effects,
watch CPU with the page idle and scrolled offscreen.

Reduced motion must react to changes mid-visit. framer-motion's `useReducedMotion` doesn't, so
use a `useSyncExternalStore` matchMedia subscription (snippet in `workflows/chapter-rail.md`). Test
it by toggling `page.emulateMedia({ reducedMotion })` after the page has loaded.

