agentleFS
Sign inStart free
jhonatan-oliveiradevjhonatan-oliveiradev/agent-skills/skills/orchestrating-cinematic-web-motion/SKILL.md

orchestrating-cinematic-web-motion

Skill1 starsChanged 3 months agoMITView on GitHub

Use when a React or Next.js interface needs a coherent premium motion language involving scroll choreography, reveals, parallax, pinned scenes, hover motion, or cinematic 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:

    Ensure one property has one animation owner.

    line 29
  2. Distinctive:

    Test rapid scrolling, resize, route navigation, tab visibility changes, and mobile touch.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Orchestrating Cinematic Web Motion

Stack decision

  • CSS: simple hover/focus/tap transitions.
  • Motion: component state, layout transitions, presence, lightweight interaction.
  • GSAP + ScrollTrigger: multi-step timelines, pinned scenes, scrubbed storytelling, complex sequencing.
  • Lenis: optional smooth scroll. Use exactly one smooth-scroll engine.
  • Three.js/WebGL: only when spatial or shader behavior materially supports the concept.

Taste defaults

Motion should guide hierarchy, add depth, and preserve legibility. Prefer restrained easing and modest transforms over bounce, overshoot, or large scale jumps.

Useful defaults:

  • reveal duration: 0.7–1.0s;
  • hover: 0.25–0.5s;
  • word stagger: 0.03–0.06s;
  • grouped items: 0.05–0.10s;
  • reveal trigger near 80–85% viewport;
  • scrub around 0.8–1.3 when narrative lag helps.

Workflow

  1. Make static layout excellent first.
  2. Define motion roles: entrance, reading-order reveal, scroll narrative, direct manipulation, ambient detail.
  3. Ensure one property has one animation owner.
  4. Scope GSAP with cleanup on unmount and refresh after font/media/layout changes.
  5. Disable scrubbed and pointer-heavy behavior for reduced motion/coarse pointers where appropriate; render final states immediately.
  6. Test rapid scrolling, resize, route navigation, tab visibility changes, and mobile touch.

Avoid

  • animating every section identically;
  • stacking Motion and GSAP on the same transform;
  • initializing multiple smooth-scroll engines;
  • permanent will-change on many nodes;
  • motion that hides navigation or CTA until a long intro completes.

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.

Check your setup, free