agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/gsap-performance/SKILL.md

gsap-performance

Skill136 starsChanged 5 months agoMITView on GitHub

Diagnose GSAP and ScrollTrigger performance.

46 other projects use a version of this, 43 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use framer-motion, motion-design and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • alexsnchzSkill

    framer-motion

    Expert skill for Motion (formerly Framer Motion) — the React animation library. Use this skill whenever the user asks to animate React components, add transitions, implement gesture interactions (drag, hover, tap), create scroll-linked effects, animate route/component presence, or build shared-element transitions. Also triggers for: page transitions, spring animations, layout animations, AnimatePresence, variants, useMotionValue, useScroll, useTransform, whileHover, whileTap, stagger effects, motion values, or any 'how do I animate X in React' question. Invoke even if the user doesn't mention 'framer-motion' by name — if they want smooth UI animations in React, this skill applies.

    Also in 3 projects that use this

  • soilmassSkill

    motion-design

    Create animations and motion graphics using industry standards. Use when asked to animate UI elements, create video content, implement transitions, or build motion systems. Implements W3C Design Tokens, Material Design 3 baseline, and Lottie specification compliance.

    Also in 5 projects that use this

  • sirakinbSkill

    threejs-fundamentals

    Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.

    Also in 3 projects that use this

  • sirakinbSkill

    threejs-textures

    Three.js textures - texture types, UV mapping, environment maps, texture settings. Use when working with images, UV coordinates, cubemaps, HDR environments, or texture optimization.

    Also in 3 projects that use this

  • AnasX7Skill

    redesign-existing-projects

    Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.

    Also in 5 projects that use this

  • +7 more from sirakinb

The file

We split this skill into the rules it gives an agent

10 rules. 3 are common, 6 are distinctive, and 1 is very specific to this project.

  • 3

    Common

    Most of the 44 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer: x, y, scale, rotation, opacity.

    line 19
  2. Distinctive:

    Avoid when possible: width, height, top, left, margin, padding because they trigger layout and can cause jank.

    line 20
  3. Distinctive:

    Use will-change selectively on elements that will animate soon.

    line 26
  4. Very specific:

    Remove or narrow will-change when an element no longer needs it.

    line 32
  5. Common:

    Use stagger instead of many separate tweens with manual delays when the animation is the same.

    line 40
  6. Common:

    Prefer gsap.quickTo() for properties that update often, such as mouse-follower x/y.

    line 46
  7. Distinctive:

    Call ScrollTrigger.refresh() only when layout actually changes, such as after content load.

    line 62
  8. Common:

    Avoid animating huge numbers of properties on many elements at once.

    line 67
  9. Distinctive:

    Use gsap.quickTo() for frequently updated properties.

    line 73
  10. Distinctive:

    Create hundreds of overlapping tweens or ScrollTriggers without testing on lower-end devices.

    line 80

“Common” is measured: kept by at least 6 in 10 of the 44 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

GSAP Performance

When to Use This Skill

Apply when the affected animation uses GSAP or ScrollTrigger. Diagnose measured frame, layout/paint or lifecycle cost. Generic motion diagnosis belongs to animation-jank-qa, and a broad release review to motion-performance-qa.

Related skills: motion-performance-qa, animation-jank-qa, animation-tool-router, and reduced-motion-design.

Prefer Transform and Opacity

Animating transform (x, y, scaleX, scaleY, rotation, rotationX, rotationY, skewX, skewY) and opacity usually avoids layout and can reduce paint cost; compositor isolation depends on the browser, layer composition and effect. Measure instead of assuming GPU acceleration. Avoid animating layout-heavy properties when a transform can achieve the same effect.

  • Prefer: x, y, scale, rotation, opacity.
  • Avoid when possible: width, height, top, left, margin, padding because they trigger layout and can cause jank.

GSAP's x and y use transforms by default; use them instead of left/top for movement.

will-change

Use will-change selectively on elements that will animate soon. It hints the browser to prepare for animation work, but overusing it can increase memory pressure.

will-change: transform;

Remove or narrow will-change when an element no longer needs it.

Batch Reads and Writes

GSAP batches updates internally. When mixing GSAP with direct DOM reads/writes or layout-dependent code, avoid interleaving reads and writes in a way that causes repeated layout thrashing. Prefer doing all reads first, then all writes, or let GSAP handle the writes in one go.

Many Elements: Staggers and Lists

  • Use stagger instead of many separate tweens with manual delays when the animation is the same.
  • For long lists, consider virtualization or animating only visible items; avoid creating hundreds of simultaneous tweens if it causes jank.
  • Reuse timelines where possible; avoid creating new timelines every frame.

Frequently Updated Properties

Prefer gsap.quickTo() for properties that update often, such as mouse-follower x/y. It reuses a single tween instead of creating new tweens on each update.

let xTo = gsap.quickTo("#id", "x", { duration: 0.4, ease: "power3" }),
    yTo = gsap.quickTo("#id", "y", { duration: 0.4, ease: "power3" });

document.querySelector("#container").addEventListener("mousemove", (e) => {
  xTo(e.pageX);
  yTo(e.pageY);
});

ScrollTrigger and Performance

  • pin: true pins the trigger element during the active range; it is not a GPU-promotion guarantee. Pin only the intended surface and inspect spacing and surrounding layout.
  • Numeric scrub sets catch-up smoothing (seconds). Animation can continue after scrolling stops; it does not inherently reduce work. Measure total frame cost and responsiveness on relevant devices.
  • Call ScrollTrigger.refresh() only when layout actually changes, such as after content load. Debounce refresh calls when possible.

Reduce Simultaneous Work

  • Pause or kill off-screen or inactive animations when they are not visible, such as when the user navigates away.
  • Avoid animating huge numbers of properties on many elements at once; simplify or sequence if needed.

Best Practices

  • Animate transform and opacity where possible; use will-change only on elements that actually animate.
  • Use stagger instead of many separate tweens with manual delays when the animation is the same.
  • Use gsap.quickTo() for frequently updated properties.
  • Clean up or kill off-screen animations; call ScrollTrigger.refresh() when layout changes, debounced when possible.

Do Not

  • Animate width, height, top, or left for movement when x, y, or scale can achieve the same look.
  • Set will-change or force3D on every element just in case; reserve them for elements that actually need them.
  • Create hundreds of overlapping tweens or ScrollTriggers without testing on lower-end devices.
  • Ignore cleanup; stray tweens and ScrollTriggers keep running and can hurt performance and correctness.

Technical semantics: GSAP ScrollTrigger. Verify the installed version for implementation details.

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.