AI creators have a distribution problem the rest of LinkedIn does not: your best work, a prompt stack, a Claude Code workflow, a token-saving trick, lives in a code block or a terminal that scrolls past in half a second. A LinkedIn carousel is a swipeable slide deck you upload to the feed as a PDF, one idea per slide, built to be saved and swiped back through instead of skimmed once, which is exactly what a dense AI how-to needs. We pulled every document carousel across 531 posts from 5 of the biggest AI creators, run on 2026-07-20, and clustered them into six repeatable structures, each with its own slide-count range and its own way to close.
What a LinkedIn carousel actually is
A carousel is not a gallery of separate images, it is one multi-page PDF a reader taps through, and it is the AI creator's best format for a reason: a prompt stack or a tool workflow is dense, and a deck forces someone to slow down and save it. It is one part of the wider templates library. Whether you are a builder sharing workflows or a creator growing an audience under your own name, a carousel gives a dense idea room to land. Building a personal brand rather than teaching AI? See the carousel templates for personal brands.
We pulled every document carousel these 5 AI creators distributed across 531 posts, Allie K Miller, Ruben Hassid, Charlie Hills, Nate Herkelman, and Maja Voje (four of them post carousels, Ruben Hassid does not), and found six repeatable structures. Each one is a slide-by-slide skeleton plus two real, verbatim examples (a deck's cover title) with a link to the live post and its real slide count.
A count, then one hack or prompt per slide.
Walk a tool workflow, one step per slide.
Test the tools, keep the best, one per slide.
React to a launch or leak, decode it slide by slide.
Real numbers, one finding per slide.
Five to eight slides, one reframable idea.
The 6 carousel structures
Each structure is a slide-by-slide skeleton followed by two real document carousels that used it, with their real slide count and reactions. Swap the brackets for your own specifics, honor the slide-count range, and keep the order.
1. The Numbered Hacks & Prompts List
The AI creator's default, and for good reason: a numbered prompt list or hack dump is the single most saveable thing you can post, because a reader wants the whole list in one file to work through later. State the exact count on the cover, then give one hack, prompt, or rule its own slide. Run it at 7 to 14 slides for a standard list, with dense hack dumps stretching past 30. Nate Herkelman fit 32 Claude Code Hacks into 9 slides and stacked 18 Token Hacks across 36, while Maja Voje ran 15 GTM Prompts for Claude Opus 4.8 in a tight 7. Restate the number on-slide and give every entry one concrete detail, a real command, a copy-ready prompt, an exact setting.
- 1Slide 1 (cover)[exact number] + [the prompt, hack, or tool payoff the reader wants]
- 2Slide 2 to N-1one numbered entry per slide, "[#]. [the hack]" + the exact command, prompt, or setting, readable in isolation, name and @handle restated
- 3Last slidethe final entry IS the close, or a light wrap: "Which one are you trying first?" / "Save this."
| Carousel | Slides | Reactions |
|---|---|---|
| 32 Claude Code Hacks | 9 | 581 |
| 15 GTM Prompts for Claude Opus 4.8 | 7 | 131 |
2. The Step-by-Step System
AI moves in workflows, so walk one, cover to close, one step per slide. This is where you turn a tool stack (a CLAUDE.md file, a skill, a QA agent, an Airtable base) into a system a reader can rebuild. Plan for 7 to 12 slides, longer when a setup has more moving parts. Charlie Hills broke his branded-carousel build into an 11-slide, 9-step workflow in Create Carousels with Claude Code, and Nate Herkelman turned token discipline into a 7-slide fix in How to Never Hit Your Claude Limit Again. Label and order every step, and drop a pro-tip slide where a step has a gotcha.
- 1Slide 1 (cover)the outcome as a promise, "Create carousels with Claude Code"
- 2Slide 2the stack or the stakes: the tools you will wire together, or the cost of not
- 3Slide 3 to N-1one ordered step per slide, labeled "Step 1...", "Step 2...", one concrete detail per step (an exact prompt, a file name, a tool), with a pro-tip slide where a step has a gotcha
- 4Last slideproof it works (a real result, a before and after) + one CTA (comment a keyword, watch the walkthrough)
| Carousel | Slides | Reactions |
|---|---|---|
| Create Carousels with Claude Code | 11 | 738 |
| How to Never Hit Your Claude Limit Again | 7 | 328 |
3. The Curated Roundup
Instead of one opinion, curate a set: the tools, skills, models, or interaction patterns worth knowing, one per slide. It works because "I tested these so you don't have to" is credibility a single tip cannot buy. Run it at 7 to 12 slides, following item count. Nate Herkelman tested more than 100 skills and kept the 6 that mattered in I Tried 100+ Claude Code Skills. These 6 Are The Best., a 10-slide roundup, and Allie K Miller mapped all four Claude Code interaction patterns in 4 Ways to Work on Multiple Tasks with Claude Code, the highest-reach deck in our set at 797 reactions. Keep every entry uniform and lead with how you vetted them.
- 1Slide 1 (cover)the scope + your vetting, "I tried 100+, these 6 are the best"
- 2Slide 2 to N-1one curated entry per slide (one tool, one skill, one pattern), uniform in layout: what it does + when to use it
- 3Last slidethe pattern across the entries, or a save CTA
| Carousel | Slides | Reactions |
|---|---|---|
| I Tried 100+ Claude Code Skills. These 6 Are The Best. | 10 | 595 |
| 4 Ways to Work on Multiple Tasks with Claude Code | 7 | 797 |
4. The News-jack / Reveal
AI news breaks weekly, and a carousel is how you turn a moment into saved authority. React to a launch, a leak, or a trend, then decode what it means one slide at a time. Keep it 5 to 10 slides so it stays timely. Nate Herkelman read the leaked codebase and pulled the insights that mattered in Claude Code's Source Code Just Leaked... across 9 slides, and turned a wave of no-code founders into a trend read in How Claude is Creating a New Generation of Millionaires in 5. Borrow the reach of the event, but make the takeaway yours.
- 1Slide 1 (cover)the event + a stakes line, "X just happened, here's what it means"
- 2Slide 2what happened, in one concrete beat
- 3Slide 3 to N-1one implication or insight per slide, each with a specific detail
- 4Last slideyour take, or the move to make now
| Carousel | Slides | Reactions |
|---|---|---|
| Claude Code's Source Code Just Leaked... | 9 | 549 |
| How Claude is Creating a New Generation of Millionaires | 5 | 238 |
5. The Data / Report Drop
When you have real numbers, a survey, a benchmark, an experiment log, let the data carry the deck. One finding per slide, each with its figure. These run long by design, 20 to 36 slides, because every cut deserves its own frame. Charlie Hills turned a 200-leader enterprise survey into The Ultimate Enterprise AI Governance Report across 30 slides, and Nate Herkelman logged a live trading experiment in Opus 4.7 Trading Bot over 28. Put the headline number on the cover and keep each entry uniform.
- 1Slide 1 (cover)the source + the headline number, "200 leaders surveyed, here's what they said"
- 2Slide 2 to N-1one finding or data cut per slide, the number first, then the one-line read
- 3Last slidethe pattern across the data + a takeaway or save CTA
| Carousel | Slides | Reactions |
|---|---|---|
| The Ultimate Enterprise AI Governance Report | 30 | 422 |
| Opus 4.7 Trading Bot | 28 | 411 |
6. The Single-Idea Punch
Sometimes the whole deck is one idea a reader needs to sit with: a mindset shift, a single unlock, a "you can do this too" story. Five to 8 slides, one thread, no numbered list. Nate Herkelman made the case for running Claude Code without paying for tokens in Claude Code for Free across 7 slides, and turned one 18-year-old's exit into a builder's blueprint in $100M Vibe Coded App, also 7. It wins on the strength of a single reframable line, so spend the cover on that line and let the rest land the point.
- 1Slide 1 (cover)one line, a claim or a provocation, no number
- 2Slide 2the whole idea: setup, reframe, why it matters now
- 3Slide 3 to N-1one proof or one sub-point per slide, concrete
- 4Last slidethe reframe restated, or a soft next step
| Carousel | Slides | Reactions |
|---|---|---|
| Claude Code for Free | 7 | 304 |
| $100M Vibe Coded App | 7 | 190 |
6 rules for AI carousels that get saved
These structures do the slide-by-slide work. To fill them fast, CaptureFlow turns one capture, a voice note, a screen recording, a messy doc, into a finished carousel and every other format it distributes. CaptureFlow is an AI content agent that turns your expertise into weeks of on-brand content for every platform, and a carousel is one of the outputs it produces. Whatever drafts it, the same rules decide whether an AI carousel gets saved:
- One idea per slide. If a prompt needs a setup line and the prompt itself, that is two slides, not one cramped one.
- The cover carries the click. Put the exact number or the tool name in it, a prompt list dies without its count, and back it with a stakes line (a real result, a leaked source, a survey size).
- Make every slide copy-ready. The number one reason AI decks get saved is that a reader wants the real command or prompt in their pocket, so put the exact text on the slide, not a paraphrase.
- Match the slide count to the structure, not a flat number. A 5-slide reveal and a 30-slide report drop both outperform, so let the archetype set the length.
- Keep the count honest. If the cover says 32 hacks, deliver 32. A broken promise trains people to scroll past your next deck.
- Keep your name and @handle on every slide. When a prompt slide gets screenshotted into a group chat, that byline is what sends people back to you.
How to turn an AI workflow into a carousel
- 1
Pick the structure that fits what you have: a numbered list for a prompt or hack stack, the step-by-step for a tool workflow, the roundup for a tools or skills test, the news-jack for a launch or leak, the report drop for real data, or the single-idea punch for one reframe.
- 2
Write the cover first. It is the only slide the feed shows, so put the exact count or the tool name in it and add a stakes line under the promise.
- 3
Map one idea to each slide with the skeleton, keep every command or prompt copy-ready, honor the structure's slide-count range, and pick your close on purpose.
- 4
Short on time, outline the deck in the free Carousel Outliner, draft the slide copy in the LinkedIn post generator, then sharpen your cover line in the hook generator until it stops the scroll.
The takeaways
- 01A LinkedIn carousel is a swipeable PDF slide deck built to be saved and swiped back through, the format that finally makes a dense prompt list or tool workflow easy to keep.
- 02The 6 structures that earned the most reactions across 531 AI-creator posts: the Numbered Hacks and Prompts List, the Step-by-Step System, the Curated Roundup, the News-jack or Reveal, the Data or Report Drop, and the Single-Idea Punch.
- 03AI decks over-index on two shapes: numbered prompt or hack lists and step-by-step tool workflows, because both are built to be saved and rebuilt.
- 04Slide count is structure-specific: reveals win in 5 to 10 slides, report drops stretch to 20 to 36, and standard lists sit at 7 to 14.
- 05The cover carries the click, so put the exact count or the tool name in it, and make every middle slide copy-ready with the real command or prompt.
- 06Reach decks close on a reframe or the one insight that reorders how someone works, lead-gen decks close on comment-to-unlock, pick one on purpose.
Turn these into posts
Frequently asked questions
- What makes a good AI carousel on LinkedIn?
- The best AI carousels turn something that normally lives in a terminal or a code block, a prompt stack, a Claude Code workflow, a token-saving trick, into one saveable file. Put the exact count or tool name on the cover, give each hack, prompt, or step its own slide, and make every slide copy-ready with the real command instead of a paraphrase. Across 531 posts from 5 top AI creators, the numbered list and the step-by-step workflow were the two most common shapes, because both are built to be saved and rebuilt.
- How many slides should an AI carousel have?
- It depends on the structure. Across the AI decks we studied, single-idea reveals won in 5 to 10 slides, curated roundups and step-by-step workflows sat at 7 to 12, standard prompt and hack lists ran 7 to 14, and data or report drops stretched to 20 to 36 because each finding wanted its own slide. Keep one idea per slide and make the cover promise exactly what the deck delivers.
- Should I put my actual prompts in the carousel?
- Yes. The number one reason an AI deck gets saved is that a reader wants the real command or prompt in their pocket, so put the exact text on the slide, not a summary of it. Maja Voje's 15 GTM Prompts for Claude Opus 4.8 and Nate Herkelman's 32 Claude Code Hacks both work because the reader can copy each entry straight off the slide. If a prompt needs a setup line, give it two slides rather than cramming.
- Can I turn one AI workflow into a carousel without designing every slide?
- Yes. Start from a structure above, then let AI handle the slide breakdown and the copy. CaptureFlow is an AI content agent that turns your expertise into weeks of on-brand content for every platform, so one voice note, screen recording, or doc can become a full carousel plus the other formats you distribute, all in your own voice.