agentleFS
divyanshu-iitiandivyanshu-iitian/agent-website-design-skills/product-motion-design/SKILL.md

product-motion-design

Skill2 starsChanged 4 months agoMITView on GitHub

Design, implement, audit, or repair purposeful motion for React and web interfaces, including GSAP timelines, scroll choreography, micro-interactions, and optional Three.js scenes, with cleanup, responsive behavior, reduced-motion support, and browser verification.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use motion to explain hierarchy, causality, state, and spatial relationships.

    line 8
  2. Very specific:

    Keep layout stable. Animate transform and opacity where possible.

    line 17
  3. Distinctive:

    Verify real pixels, interaction, resize behavior, and nonblank canvas output at mobile and desktop widths.

    line 19
  4. Distinctive:

    Do not add cursor-following effects to touch-only experiences or controls requiring precision.

    line 28
  5. Very specific:

    Read references/motion-checklist.md before shipping GSAP, scroll-linked, or Three.js work.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product Motion Design

Use motion to explain hierarchy, causality, state, and spatial relationships. Do not animate a page merely to make it look expensive.

Workflow

  1. Identify the user task, focal action, state changes, and moments where motion can improve comprehension.
  2. Define a motion hierarchy: page entrance, section reveal, component transition, feedback, and ambient motion.
  3. Choose the lightest mechanism that fits: CSS for simple states, the existing React animation library for component lifecycle, GSAP for coordinated timelines or scroll, and Three.js only for a real 3D requirement.
  4. Establish duration, easing, distance, stagger, interruption, and reduced-motion rules before implementation.
  5. Scope animation selectors to component roots. Register plugins once and clean timelines, observers, listeners, frames, geometries, materials, textures, and renderers on teardown.
  6. Keep layout stable. Animate transform and opacity where possible; avoid perpetual main-thread work and broad transition: all.
  7. Adapt density and choreography for touch, narrow containers, low-power devices, and hidden tabs.
  8. Verify real pixels, interaction, resize behavior, and nonblank canvas output at mobile and desktop widths.

Motion Rules

  • Interaction feedback is immediate; decorative motion yields to input.
  • Scroll animation must preserve reading order and usable content without JavaScript.
  • Repeated lists use restrained stagger and a cap; they do not replay on every tiny scroll.
  • 3D scenes cap pixel ratio, pause when hidden, resize from the actual container, and provide a static reduced-motion frame.
  • Theme changes must update 3D materials and backgrounds without making the focal object disappear.
  • Do not add cursor-following effects to touch-only experiences or controls requiring precision.

Delivery Contract

Return or implement:

  1. Motion intent - what each animation communicates.
  2. Choreography - triggers, sequence, timings, and interruption behavior.
  3. Implementation - scoped code using the existing stack.
  4. Performance contract - cleanup, device adaptation, and rendering budget.
  5. Accessibility - reduced-motion and no-JavaScript behavior.
  6. Proof - browser observations or screenshots at relevant states and viewports.

Reference

Read references/motion-checklist.md before shipping GSAP, scroll-linked, or Three.js work.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.