What problem does it solve? Modern web animations often pull in heavy JavaScript libraries like GSAP or Framer Motion for effects that native CSS now handles natively, adding bundle weight and complexity. This Skill helps you decide when pure CSS is sufficient and provides production-ready patterns for scroll-driven animations, view transitions, enter/exit animations, and anchor-positioned floating UI. ## Core Features & Use Cases - Decision Framework: A clear comparison table for choosing CSS native vs GSAP vs Framer Motion based on animation complexity, so you avoid unnecessary dependencies. - Modern CSS Patterns: Ready-to-use code for scroll-driven animations (animation-timeline), View Transitions API (same-document and cross-document), @starting-style enter animations, and CSS anchor positioning for tooltips and popovers. - Fallbacks & Browser Support: A references file with current browser support tables, @supports progressive enhancement strategies, and accessibility rules for prefers-reduced-motion. - Use Case: You are building a marketing page with scroll-reveal sections and an animated dialog. Instead of installing an animation library, apply animation-timeline: view() for reveals and @starting-style with allow-discrete for the dialog, with graceful fallbacks for older browsers. ## Quick Start Ask the AI to add a scroll-driven fade-in reveal animation to a section using pure CSS with a fallback for unsupported browsers.