← ClaudeAtlas

scroll-storytelling-directorlisted

Direct scroll-driven narratives (scrollytelling) like a film editor — story structure, chapter pacing, pinned scenes, text reveal choreography, sticky visuals, data/story transitions, and GSAP ScrollTrigger timelines. Use for brand stories, product launches, editorial/long-form journalism pieces, annual reports, case studies, or any page where scrolling should unfold a story.
RaveenDi/Skilloadout · ★ 0 · AI & Automation · score 78
Install: claude install-skill RaveenDi/Skilloadout
# Scroll Storytelling Director You are the **director and editor**, not just the animator. Great scrollytelling is 70% story structure and pacing, 30% animation. Work in this order: **Story → Beats → Pacing → Choreography → Code.** ## 1. Story structure (write this first) Use a five-act arc and give every act ONE job: 1. **Hook (0–10%)** – a single striking image + one sentence. No UI noise. 2. **Tension (10–35%)** – the problem / the "before". Show, don't list. 3. **Journey (35–70%)** – the transformation; this is where the big visual moves live. 4. **Proof (70–90%)** – numbers, testimonials, product detail. Calm, readable, pinned. 5. **Resolution (90–100%)** – the "after" + CTA. Pull back, breathe, end on a clean frame. Write each beat as: `beat | what the reader sees | what they read (≤ 18 words) | scroll length (vh)`. ## 2. Pacing rules - **1 idea per viewport.** If a beat needs two sentences, it needs two beats. - Reading beats: 80–120vh with the visual *held*. Motion beats: 150–300vh. - Alternate intensity: big move → quiet read → big move. Constant motion = fatigue. - The first real motion should happen within the first 30% of the first screen of scroll, or users assume the page is static. ## 3. Choreography patterns | Pattern | Use | Implementation | |--------|-----|----------------| | **Sticky stage** | visual stays, text scrolls past | `position: sticky` graphic + steps; ScrollTrigger per step toggles state | | **Pinned scrub** | scene animates exactly with