BjornMelin/dev-skills / plugins/web-motion/skills/gsap-performance
gsap-performance
VerifiedOfficial 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.0 KB |
| agents/openai.yaml | config | 337 B |
| assets/examples/gsap-performance-starter.md | markdown | 234 B |
| assets/templates/gsap-performance-audit-report.md | markdown | 639 B |
| assets/templates/gsap-performance-review-checklist.md | markdown | 1.3 KB |
| evals/evals.json | config | 3.9 KB |
| evals/trigger-queries.json | config | 4.1 KB |
| references/index.md | markdown | 543 B |
| references/layer-budget-and-will-change.md | markdown | 2.3 KB |
| references/official-source.md | markdown | 1.5 KB |
| references/profiling-playbook.md | markdown | 2.3 KB |
| references/property-cost-matrix.md | markdown | 1.5 KB |
| references/provenance.json | config | 1.9 KB |
| references/scroll-performance.md | markdown | 1.5 KB |
| references/source-ledger.md | markdown | 1.6 KB |
| scripts/audit.mjsexecutable | script | 23.1 KB |
references/profiling-playbook.md
View on GitHub# GSAP profiling and evidence playbook
Skill: gsap-performance
Checked at: 2026-06-04
## When To Load
- Read when a GSAP issue is described as jank, dropped frames, layout thrash, or slow scroll.
## Source Anchors
- https://gsap.com/docs/v3/GSAP/gsap.to()
- https://gsap.com/docs/v3/Plugins/ScrollTrigger/
## Reference Notes
- Start from evidence: browser performance profile, visible reproduction, affected route, device/browser, and animation trigger path.
- Classify costs as JavaScript, style recalculation, layout, paint, composite, image/decode, or scroll workload before suggesting an engine change.
- Use the audit CLI for leads, then verify each finding against runtime behavior.
## Focused Checks
- Capture before/after evidence for at least the hot interaction.
- Check frame budget under reduced CPU or representative device when the surface is user-facing.
## Failure Modes
- Replacing a library without first identifying the bottleneck.
- Treating `will-change` as a blanket fix.
## Operating Guidance
GSAP performance audits: transform/opacity, layout thrash, ScrollTrigger batching, repeat loops, will-change, and frame pressure.
### Decision Boundaries
- Use web-three-r3f or typegpu for GPU/canvas rendering performance.
- Use web-css-animations for CSS-only transition audits.
- Use gsap-scrolltrigger for scroll scene semantics.
### Workflow Details
1. Find hot paths and animated properties.
2. Classify layout, paint, composite, and JavaScript costs.
3. Run audit scan and inspect high-confidence findings.
4. Recommend transform/opacity, batching, throttling, or engine changes only with evidence.
### Gotchas
- will-change is a scoped hint, not a global optimization.
- ScrollTrigger refresh calls after layout changes need ordering, not random timeouts.
- Infinite tweens need reduced-motion and cleanup behavior.
## Validation Notes
- Inspect installed package versions and local architecture before applying examples.
- Prefer the bundled `scripts/audit.mjs doctor --root <repo> --format json` command when setup is unclear.
- Use `scripts/audit.mjs scan --root <repo> --format markdown` for repeatable static findings, then manually verify every finding against current code.
- Close with repo-specific checks and user-visible runtime proof when this skill affects a rendered surface.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |