fixing-motion-performance

Fix animation performance issues. /fixing-motion-performance Apply these constraints to any UI animation work in this conversation. /fixing-motion-performance Review the file against all rules below and report: Do not migrate animation libraries unless explicitly requested. Apply rules within the existing stack. Reference these guidelines when: - /fixing-motion-performance Apply these constraints to any UI animation work in this conversation. - /fixing-motion-performance Review the file against all rules below and report: - violations (quote the exact line or snippet) - why it matters (one short sentence) - a concrete fix (code-level suggestion) - adding or changing UI animations (CSS, WAAPI, Motion, rAF, GSAP) - refactoring janky interactions or transitions - implementing scroll-linked motion or reveal-on-scroll - animating layout, filters, masks, gradients, or CSS variables - reviewing components that use will-change, transforms, or measurement - composite: transform, opacity - paint: color, borders, gradients, masks, images, filters - layout: size, position, flow, grid, flex - do not interleave layout reads and writes in the same frame - do not animate layout continuously on large or meaningful surfaces - do not drive animation from scrollTop, scrollY, or scroll events - no requestAnimationFrame loops without a stop condition - do not mix multiple animation systems that...