1---2name: carousel-narratives3description: Use when writing a multi-slide carousel post for Instagram, LinkedIn, or similar — for any niche or business — including repurposing scripts/blogs into slides or diagnosing low saves and swipe-through.4---56# Carousel Narratives78- A carousel is a story told one swipe at a time. Each slide's only job is to make the thumb swipe to the next.9- Slide 1 is a hook (treat it like a thumbnail + title); the last slide is the bookend + call to action.10- Built on the six levers — see **storytelling-hooks**. Recap: 1. Curiosity gap · 2. Emotional mirror · 3. Conflict engine · 4. Relatability · 5. Pattern + surprise · 6. Three-act.1112## When to Use1314- Writing an Instagram or LinkedIn carousel (5–10 slides).15- Repurposing a video script, blog, or tip list into a swipeable post.16- Diagnosing a carousel with high reach but low saves/swipe-through.17- Any niche: education, business, design, finance, fitness, faith, personal brand.1819## Generation Workflow20211. **Intake.** Confirm: exact audience, goal metric (saves / shares / comments / follows), platform(s), voice, and rough slide count. Ask if missing when the user can respond; otherwise state assumptions up front.222. **Map.** Assign every idea to the slide map below. **One idea per slide wins over a shorter deck** — split a crowded slide rather than compress it (5–10 slides total).233. **Write.** Deliver slide-by-slide: **slide text + visual direction** (layout intent, emphasis, swipe cue — not fonts/hex codes) for each slide, then the caption. Read **patterns.md** (same folder) for slide-1 hooks, transition loops, CTA lines, and caption openers — adapt, don't copy.244. **Adapt per platform** (below) if posting to more than one.255. **Check** against the checklist and say so.2627## Platform Deltas (Instagram vs LinkedIn)2829| | Instagram | LinkedIn |30|---|-----------|----------|31| Format | 4:5 (1080×1350) image slides | PDF document post, square or 4:5 |32| Text density | ~2-second skim per slide | Tolerates ~20–30% more text; add one supporting example |33| Tone | Casual, emoji fine | Peer-to-peer professional, minimal emoji |34| Best CTA | Save (reference value) | Comment — comments drive LinkedIn reach more than saves |35| Caption | Hook line + compressed story + 3–5 hashtags | First-person story opening; 2–3 hashtags max |3637- Posting to both? Write **one core deck + a short adaptation layer** per platform (headline variant, CTA variant, density note, and its own caption + hashtags) — don't design twice.38- Slide count from a list: N items → N value beats + hook + stakes + payoff = **N + 3 slides**.3940## Slide Map (Quick Reference)4142| Slide | Role | Lever focus |43|-------|------|-------------|44| 1 | Hook — stop the scroll, open the loop | 1, 4, 2 |45| 2 | Stakes — why this matters to *you* | 3, 4 |46| 3–N−1 | Value beats — one idea per slide | 5, 6 |47| N | Payoff + CTA + bookend | 6, 1 |4849## Slide 1: The Hook5051- One bold idea, large readable text, minimal words.52- Open a curiosity gap wrapped in a relatable feeling — same job as a video hook.53- Add a swipe cue ("swipe →", an arrow, or a sentence that cuts off).54- Patterns: bold claim, surprising stat, "Stop doing X", "N mistakes that…", a question that's clearly "about me".5556## Slide 2: The Stakes5758- Convert the hook's gap into *personal* stakes: why this costs or blocks the reader specifically.59- Reframe the problem away from the reader's self-blame ("you're not underpaid because you lack skill — it's how you price").60- End on momentum into the first value beat.6162## The Swipe-Momentum Rule6364- **One idea per slide.** Two ideas = a reason to stop.65- End slides on a **mini open loop**: "...but there's a catch →".66- Keep each slide skimmable in ~2 seconds; the deck readable in ~15.67- Maintain a visual rhythm (consistent layout) so cognitive load stays low and the thumb keeps moving.6869## The Middle (Value Beats)7071- Each beat = a small three-act: claim → why → quick proof/example.72- Use **pattern + surprise** on at least one slide to create a memorable jolt.73- Order beats by rising value or rising tension; don't front-load the best and flatten after.74- Numbers and specifics make beats sharp ("cut 3 steps" > "simplify").7576## Final Slide: Payoff + CTA7778- Resolve the loop opened on slide 1 (bookend — echo the opening phrase/number).79- **One** CTA only: save, share, comment a keyword, or follow. Pick the action that fits the goal:80 - Save → reference/how-to value.81 - Share → relatable/identity statement.82 - Comment → a question or keyword prompt.83- Make the action effortless and explicit.8485## Caption Pairing8687- The caption is a second hook for the feed preview — open a loop in the first line.88- Expand the story the slides compressed; end with the same CTA as the last slide.8990## Common Mistakes9192| Mistake | Fix |93|---------|-----|94| Two ideas squeezed onto one slide to keep the deck short | Split the slide — one idea per slide beats a shorter deck |95| Same deck posted identically to IG and LinkedIn | One core deck + per-platform adaptation layer |96| Slide text only, no visual direction | Every slide gets layout intent + emphasis + swipe cue |97| CTA chosen by habit ("follow!") | Match CTA to goal *and* platform (save on IG, comment on LinkedIn) |98| Caption written as an afterthought | First caption line is its own hook; caption expands what slides compressed |99| Best beat placed first, deck flattens after | Order beats by rising value or tension |100101## Carousel Checklist102103- [ ] Does slide 1 stop the scroll and open a loop in ~2 seconds?104- [ ] Exactly one idea per slide?105- [ ] Does each slide end on momentum toward the next swipe?106- [ ] At least one pattern-break beat in the middle?107- [ ] Final slide pays off slide 1 (bookend) + a single clear CTA?108- [ ] First caption line is its own hook?109- If swipe-through is low: slide 1 is weak or a middle slide stalls — find the slide that closes a loop without opening one.110111## Related112113- **storytelling-hooks** — the six levers (read for depth).114- **email-hooks** — the same loop logic for inboxes.