agentleFS
frankxaifrankxai/awesome-motion-design-agent-skills/skills/motion-director/SKILL.md

motion-director

Skill111 starsChanged 11 days agoCC0-1.0View on GitHub

Use when designing motion concepts, animation systems, choreography, timing, easing, reduced-motion behavior, or deciding which motion stack to use for web UI, video, GIF, Rive, Lottie, GSAP, Motion, Remotion, or Three.js work.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Prefer transform and opacity, and name transition properties explicitly.

    line 28
  2. Distinctive:

    Read the current Motion documentation or GSAP documentation for the installed runtime before changing APIs.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

Motion Director

Workflow

  1. Identify the output target: product UI, landing page, social video, GIF, design prototype, or embedded animation asset.
  2. Define the job of motion: guide attention, explain state, create delight, teach a concept, or express brand.
  3. Inspect the existing implementation and choose the lightest suitable stack:
    • Native CSS transitions for simple hover, press, and state feedback.
    • Motion for React UI state and layout transitions.
    • GSAP for timelines, scroll, SVG, text, and high-control choreography.
    • Rive for interactive state-machine animation.
    • Lottie for portable vector loops.
    • Remotion for rendered video/GIF.
    • Three.js for spatial/3D scenes.
  4. Specify timing tokens, easing, stagger rules, and reduced-motion behavior.
  5. Patch the owned code, or provide a concrete handoff if this session cannot write it. Do not start another agent without authorization.
  6. Capture output and use the bundled motion quality rubric. Leave unobserved categories unscored.

Interaction contract

  • Decide whether motion helps before adding it. Keep frequent keyboard commands immediate; never delay focus or input behind an entrance.
  • Reuse existing tokens. For occasional UI transitions, start at 150-250 ms with an ease-out curve; explain longer narrative timing separately.
  • Prefer transform and opacity, and name transition properties explicitly. Check actual browser behavior before claiming compositor acceleration.
  • Define interruption, reversal, exit, and cleanup. Repeated clicks must settle to the latest requested state.
  • Gate hover-only movement with (hover: hover) and (pointer: fine). Keep a visible keyboard focus state and touch access to every action.
  • Design reduced motion before implementation: preserve content, state, and reading order with static or gentle opacity/color feedback.
  • Pause continuous decoration when hidden or off-screen. Preserve meaningful progress and status information.

Verification and boundaries

Inspect desktop, a phone width, keyboard focus, touch behavior, reduced motion, and a transition interrupted in both directions. Cite the exact code revision and evidence paths. A build or screenshot alone cannot establish smoothness, touch behavior, or motion quality.

Read the current Motion documentation or GSAP documentation for the installed runtime before changing APIs. This skill supplies direction; it does not install a renderer or grant permission to spend, publish, or change unrelated files.

Output Shape

Return:

  • Motion goal
  • Recommended stack
  • Choreography
  • Timing/easing tokens
  • Reduced-motion path
  • Implementation notes
  • QA checklist

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.