What problem does it solve?
Building scroll-driven data stories often results in decorative parallax, scrolljacking, broken mobile layouts, and inaccessible animations that obscure rather than reveal evidence. This Skill provides a structured workflow for deciding when scrollytelling is justified, modeling scenes as data contracts, and implementing them with the lightest reliable stack.
Core Features & Use Cases
- Technique Selection: Choose between graphic sequences, animated transitions, pan-and-zoom, moviescrollers, parallax depth layers, sticky side-by-side layouts, and stacked mobile fallbacks based on what the evidence requires.
- Scene Contracts: Model every scene as structured data with trigger ranges, data layers, annotations, reduced-motion fallbacks, and static key frames before writing implementation code.
- Implementation Guidance: Select the lightest stack from native CSS sticky positioning and IntersectionObserver through Scrollama, GSAP ScrollTrigger, Motion useScroll, D3, Canvas2D, and WebGL, with performance and accessibility guardrails.
- Use Case: A journalist wants a sticky map that flies between regions as the reader scrolls through a story. The Skill produces a scene contract with trigger ranges, a reduced-motion fallback, a mobile stacked variant, and a Scrollama-based implementation plan.
Quick Start
Ask the assistant to design a scrollytelling data story with a sticky chart that transitions as the reader scrolls, including accessibility fallbacks and a mobile layout.