gsap-performance

Optimize GSAP animations with transforms and opacity for 60fps performance.

Updated Mar 18, 2025
One-click install
npx skills add https://github.com/utsavm81098/88-residences --skill gsap-performance-utsavm81098
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsap-performance
Source: https://github.com/utsavm81098/88-residences/tree/main/.agents/skills/gsap-performance
Command: npx skills add https://github.com/utsavm81098/88-residences --skill gsap-performance-utsavm81098

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GSAP performance is often hindered by layout thrashing; this skill guides developers to focus on transforms and opacity to keep animations smooth and GPU-accelerated where possible.

Core Features & Use Cases

  • Guidance on property choice: prioritize transform and opacity to avoid layout recalculation.
  • Performance patterns: use will-change, batching reads/writes, and timeline reuse to minimize reflows.
  • Use cases: for interactive UI, scroll-based animations, and complex timelines that must stay fluid.

Quick Start

Refactor a GSAP animation to rely on transform and opacity instead of layout properties and apply will-change to the animated element.

Frequently Asked Questions about gsap-performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my GSAP animation stutter and drop frames during scroll interactions?▼

GSAP animation stutter usually happens because of layout thrashing. You can fix this by prioritizing transform and opacity properties to avoid layout recalculation and keep animations smooth.

How do I optimize GSAP animations for 60fps performance?▼

To optimize GSAP animations for 60fps, prioritize transform and opacity properties, apply will-change appropriately, and reuse timelines to minimize reflows and maintain smooth rendering.

When should I use will-change in GSAP scroll-based animations?▼

Use will-change in GSAP scroll-based animations when you need to hint the browser about upcoming property changes. Apply it appropriately to animated elements to ensure fluid GPU-accelerated rendering.

What is the best way to batch GSAP reads and writes to prevent layout thrashing?▼

The best way to prevent layout thrashing is batching GSAP reads and writes separately. This pattern stops the browser from forcing layout recalculation during complex timeline sequencing.

Can I animate layout properties instead of transforms for interactive UI elements?▼

Animating layout properties like width or top causes reflows and hurts performance. You should refactor GSAP animations to rely on transform and opacity instead to keep interactive UI fluid.