About this Skill
Keep web animations inside the frame budget — animate composite-only properties, keep motion off the main thread when the page is busy, and find the cause when an animation drops frames. Covers the layout/paint/composite pipeline, cheaper property swaps, CSS vs WAAPI vs requestAnimationFrame, Framer Motion's hardware-accelerated path, React re-rendering per frame, inherited CSS variable recalculation, blur cost, and when `will-change` actually helps. Use when an animation is janky, choppy, stutters, or drops frames; when choosing which property to animate; when deciding between CSS and JS animation on performance grounds; or when reaching for `will-change` or GPU layers. For choosing easing, duration, or whether to animate at all use animate; for reviewing motion as a whole use review-animations.
Why we picked it
Summarized from the original emilkowalski/skills SKILL.md by Emil Kowalski; the original upstream instructions were used.
What it helps with
- Use this workflow when the task matches the original Animation Performance instructions.
Before you use it
- Read the original SKILL.md and referenced files in emilkowalski/skills.
Sources & references
Original sources are linked below. Practical starting points are editorial suggestions from SkillHey.