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

site-motion-excellence-director

Skill111 starsChanged 12 days agoCC0-1.0View on GitHub

Use when planning, auditing, specifying, implementing, or improving premium website/app motion across FrankX, Arcanea, Starlight, or Vercel/Next.js sites. Use for motion design systems, site choreography, scroll motion, generated media integration, runtime selection, reduced-motion planning, visual QA, and turning rough motion ideas into implementation-ready specs.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈17

    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 this skill before adding substantial motion to a website or app.

    line 8
  2. Distinctive:

    Write a beat sequence: setup, trigger, primary move, secondary support, hold, final state.

    line 16
  3. Distinctive:

    Verify with browser screenshots, mobile, reduced motion, and video/frame proof.

    line 20
  4. Distinctive:

    Use CSS for simple state changes, hover/focus, skeletons, and low-risk reveals.

    line 25
  5. Distinctive:

    Use Motion for React for component choreography, layout transitions, presence, and React scroll work.

    line 26
  6. Distinctive:

    Use GSAP ScrollTrigger for pinned, scrubbed, snapped, SVG/canvas, or complex authored timelines.

    line 27
  7. Distinctive:

    Use Rive for interactive vector state machines.

    line 28
  8. Distinctive:

    Use Lottie/dotLottie for portable non-interactive vector loops.

    line 29
  9. Very specific:

    Use Three.js only when 3D is central and visually verified.

    line 30
  10. Distinctive:

    Use Remotion for rendered video, social variants, product explainers, and exact text/layout in media.

    line 31
  11. Distinctive:

    Do not animate a weak still frame.

    line 37
  12. Distinctive:

    Use stillness as contrast.

    line 39
  13. Distinctive:

    Keep repeated task motion short and quiet.

    line 40
  14. Distinctive:

    Do not bake exact product text into generated images or videos.

    line 41
  15. Distinctive:

    Treat mobile as separate choreography.

    line 42
  16. Distinctive:

    Never ship meaningful motion without reduced-motion behavior.

    line 43
  17. Distinctive:

    Use the bundled site motion spec for substantial site motion.

    line 47
  18. Distinctive:

    Use the bundled site motion excellence gate before handoff.

    line 49
  19. Very specific:

    Use current Motion, GSAP, or Three.js documentation for the runtime actually installed.

    line 57

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

Site Motion Excellence Director

Use this skill before adding substantial motion to a website or app.

Workflow

  1. Identify the brand, route, audience, and first user task.
  2. Define the first read before animation.
  3. Name the motion job: orient, reveal, explain, confirm, compare, express brand, or convert.
  4. Pass the still-frame gate.
  5. Write a beat sequence: setup, trigger, primary move, secondary support, hold, final state.
  6. Choose the lightest runtime that preserves the intent.
  7. Specify reduced motion in the same pass.
  8. Implement only after the spec is clear.
  9. Verify with browser screenshots, mobile, reduced motion, and video/frame proof.
  10. Score with the excellence gate.

Runtime Rules

  • Use CSS for simple state changes, hover/focus, skeletons, and low-risk reveals.
  • Use Motion for React for component choreography, layout transitions, presence, and React scroll work.
  • Use GSAP ScrollTrigger for pinned, scrubbed, snapped, SVG/canvas, or complex authored timelines.
  • Use Rive for interactive vector state machines.
  • Use Lottie/dotLottie for portable non-interactive vector loops.
  • Use Three.js only when 3D is central and visually verified.
  • Use Remotion for rendered video, social variants, product explainers, and exact text/layout in media.
  • Discover the session's actual image/video tools before choosing a generator. Check current provider documentation, access, cost, and rights; finish and QA the result in context. A provider name here is not proof of availability or authorization to spend.

Taste Rules

  • Motion is hierarchy over time.
  • Do not animate a weak still frame.
  • Make one object the hero.
  • Use stillness as contrast.
  • Keep repeated task motion short and quiet.
  • Do not bake exact product text into generated images or videos.
  • Treat mobile as separate choreography.
  • Never ship meaningful motion without reduced-motion behavior.

Required Spec

Use the bundled site motion spec for substantial site motion.

Use the bundled site motion excellence gate before handoff. Both files are included when this skill is installed alone.

Interaction and recovery

  • Preserve native reading, scrolling, focus, and touch behavior. Required content must remain available when JavaScript or a media request fails.
  • Define what happens on repeated clicks, reverse scroll, route changes, resize, hidden tabs, and preference changes. Dispose timelines, observers, and listeners when their owner unmounts.
  • Gate hover effects by pointer capability. Provide visible focus and immediate keyboard actions.
  • Reduced motion must preserve the full story in reading order. Do not initialize expensive scroll or 3D effects merely to disable them afterward.
  • Use current Motion, GSAP, or Three.js documentation for the runtime actually installed. Reuse the site's dependencies and tokens.

Evidence

Record the exact revision, desktop and phone widths, keyboard/touch observations, reduced-motion result, interrupted-transition result, and inspected video/frame sequence. Distinguish code review, automated checks, emulated input, physical-device checks, and untested behavior. Do not award an excellence score when the visual evidence is missing.

Output Shape

Return: motion thesis, first-read diagnosis, still-frame verdict, motion map, runtime choice, reduced-motion plan, implementation tasks, QA proof required, and excellence score.

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.