Skip to content
GSAP Performance

GSAP Performance Skill

GreenSock's official skill for smooth GSAP animation: animate transforms and opacity, avoid layout thrashing, use stagger and quickTo(), and keep ScrollTrigger work cheap.

GitHub Docs

Install

Install with the skills CLI

One command for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf and dozens of other agents. Needs Node.js; the skill is fetched straight from greensock/gsap-skills.

$ npx skills add greensock/gsap-skills --skill gsap-performance

Run it in a terminal. The CLI finds the agents installed on your machine, asks which ones to add the skill to, and whether to install it into the folder you ran it from or for all your projects.

Other ways to install

Copy the whole skill folder — SKILL.md and any scripts or references beside it — into ~/.claude/skills/gsap-performance/, where Claude Code picks it up in every project. Only git is needed.

tmp=$(mktemp -d) && \
  git clone --depth 1 --branch main https://github.com/greensock/gsap-skills.git "$tmp" && \
  mkdir -p ~/.claude/skills && \
  cp -R "$tmp"/skills/gsap-performance ~/.claude/skills/gsap-performance

No scripts or references next to it? Saving the SKILL.md alone as ~/.claude/skills/gsap-performance/SKILL.md works too.

Using another agent? Its personal skills folder
Codex
~/.agents/skills/
Cursor
~/.cursor/skills/
GitHub Copilot
~/.copilot/skills/
Gemini CLI
~/.gemini/skills/
Windsurf
~/.codeium/windsurf/skills/
OpenCode
~/.config/opencode/skills/

About

  • Prefer transform and opacity over layout-triggering properties
  • Targeted will-change and force3D use
  • Batch DOM reads and writes to avoid layout thrashing
  • stagger and gsap.quickTo() for many elements and frequent updates
  • ScrollTrigger pin, scrub and refresh() guidance
  • Explicit do and do-not checklists

GSAP Performance is one of GreenSock's official agent skills for the GSAP animation library, alongside the core, timeline, ScrollTrigger and React skills. It applies when an agent is optimising GSAP animations for a steady 60fps, reducing jank, or answering questions about animation performance.

Its guidance is specific. Animate transform properties (x, y, scale, rotation, skew) and opacity, which stay on the compositor, instead of width, height, top, left, margin or padding, which trigger layout. Use will-change only on elements that actually animate. Keep DOM reads and writes batched rather than interleaved. Use stagger instead of many separate tweens with manual delays, and virtualise or limit very long animated lists. For values updated on every pointer move, such as mouse followers, use gsap.quickTo(), which reuses one tween.

For ScrollTrigger it advises pinning only what is needed, using a small scrub value, and calling ScrollTrigger.refresh() only when layout really changes, debounced. It also asks the agent to pause or kill off-screen animations and clean up stray tweens and triggers. The skill ends with explicit do and do-not lists. MIT licensed.

SKILL.md

The instructions your agent loads, as published by GreenSock.

SKILL.md
name
gsap-performance
description
Official GSAP skill for performance — prefer transforms, avoid layout thrashing, will-change, batching. Use when optimizing GSAP animations, reducing jank, or when the user asks about animation performance, FPS, or smooth 60fps.
license
MIT

GSAP Performance

When to Use This Skill

Apply when optimizing GSAP animations for smooth 60fps, reducing layout/paint cost, or when the user asks about performance, jank, or best practices for fast animations.

Related skills: Build animations with gsap-core (transforms, autoAlpha) and gsap-timeline; for ScrollTrigger performance see gsap-scrolltrigger.

Prefer Transform and Opacity

Animating transform (x, y, scaleX, scaleY, rotation, rotationX, rotationY, skewX, skewY) and opacity keeps work on the compositor and avoids layout and most paint. 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 (they trigger layout and can cause jank).

GSAP’s x and y use transforms (translate) by default; use them instead of left/top for movement.

will-change

Use will-change in CSS on elements that will animate. It hints the browser to promote the layer.

will-change: transform;
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 (Stagger, Lists)
  • Use stagger instead of many separate tweens with manual delays when the animation is the same; it’s more efficient.
  • 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 (e.g. mouse followers)

Prefer gsap.quickTo() for properties that are updated often (e.g. 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 promotes the pinned element; pin only what’s needed.
  • scrub with a small value (e.g. scrub: 1) can reduce work during scroll; test on low-end devices.
  • Call ScrollTrigger.refresh() only when layout actually changes (e.g. after content load), not on every resize; debounce when possible.
Reduce Simultaneous Work
  • Pause or kill off-screen or inactive animations when they’re not visible (e.g. 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; use will-change in CSS only on elements that animate.
  • ✅ Use stagger instead of many separate tweens with manual delays when the animation is the same.
  • ✅ Use gsap.quickTo() for frequently updated properties (e.g. mouse followers).
  • ✅ Clean up or kill off-screen animations; call ScrollTrigger.refresh() when layout changes, debounced when possible.
Do Not
  • ❌ Animate width/ height/ top/ left for movement when x/ y/ scale can achieve the same look.
  • ❌ Set will-change or force3D on every element “just in case”; use for elements that are actually animating.
  • ❌ Create hundreds of overlapping tweens or ScrollTriggers without testing on low-end devices.
  • ❌ Ignore cleanup; stray tweens and ScrollTriggers keep running and can hurt performance and correctness.
Install
New

GreenSock's official skill for GSAP timelines: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control, plus the best practices and mistakes to avoid when sequencing animations.

Skill: GSAP React

by GreenSock

New

GreenSock's official skill for using GSAP in React and Next.js: the useGSAP() hook with scoped selectors and automatic cleanup, refs for targets, contextSafe callbacks, gsap.context() in useEffect, and SSR-safe usage.

Browse all skills →