agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/animation-tool-router/SKILL.md

animation-tool-router

Skill136 starsChanged 5 months agoMITView on GitHub

Resolve motion tools or native View Transitions.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when motion-tool choice is unresolved.

    line 8
  2. Distinctive:

    No dependency: static content where motion would distract or harm performance.

    line 19

≈ “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

Animation Tool Router

Use this skill when motion-tool choice is unresolved. Retain a capable existing choice; choose the lightest option that satisfies the purpose and constraints.

Routing

  • CSS transitions: hover/focus states, small fades, transforms, simple menus.
  • Motion: React component animation, layout transitions, presence, gestures, small scroll reveals.
  • GSAP: precise timelines, pinned scroll scenes, split text, SVG paths, complex choreography.
  • Lenis: smooth scroll feel when the project can support it and anchor/modal behavior is handled.
  • Native browser or supported React View Transitions: continuity when the installed router/runtime and browser floor support them; retain fallback behavior and do not force an experimental upgrade.
  • Rive or dotLottie: authored timeline or interactive state-machine assets; choose from the existing asset, runtime support and accessible fallback. Plain Lottie remains useful for compatible exported vector motion.
  • Three.js/R3F or shaders: requested spatial, material, generative or atmospheric brand visuals when their purpose and performance budget justify the cost.
  • No dependency: static content where motion would distract or harm performance.

Motion Requirements

Define:

  • purpose: reveal, continuity, depth, state, tactility, narrative, or product explanation
  • trigger: load, hover, focus, click, route, scroll, drag, or viewport
  • duration/easing
  • reduced-motion fallback
  • cleanup/unmount behavior
  • performance risks

Avoid

  • animation because the page is otherwise generic
  • scroll hijacking
  • motion that hides content
  • parallax that causes nausea or jank
  • WebGL scenes that are blank on mobile

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.