When should you use it?
- You avoid carousels because design takes too long
- You already write long-form you can mine
- You have brand colors and fonts defined
Not for: Image-heavy designs that need a designer; Brands without agreed guidelines
What do you need, and what do you get?
You need
- Your house style: palette, typefaces and voice
- Source text: newsletter excerpt, memo transcript or bullets
You get
- Six HTML slides in your brand
- A PDF ready to upload
How does it work, step by step?
- Write the brand spec onceGive colors, fonts, spacing rules and voice notes, and save them for reuse.
- Pick a slice of contentChoose one idea from a newsletter or memo rather than a whole issue.
- Ask for a fixed structureHook, four content slides, then a follow or subscribe slide.
- Render and exportOpen the HTML files, screenshot each slide and combine into a PDF.
- Do it twice by handOnly package it as a reusable skill once two or three manual runs look right.
The prompt
The original prompt by Wyndo, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Claude and Claude Code. Values in lime are placeholders.
Original prompt by Wyndo
I want to create LinkedIn carousels using HTML/CSS. Here are my brand specifications: Primary color: [your hex code], Secondary color: [your hex code], Header font: [font name and size], Body font: [font name and size], Logo: [upload your logo file], Profile photo: [upload your photo]. Save these as my carousel brand guidelines.
Exactly as published by Wyndo in How I Built LinkedIn Carousels Using Claude Skills in Less Than 5 Minutes.
Our adapted version (optional)
Using my saved brand guidelines, turn the text below into a six-slide LinkedIn carousel. Slide 1 is a hook, slides 2 to 5 each carry one point in under 30 words, slide 6 asks people to follow or subscribe. Output one HTML file per slide sized for a square LinkedIn post, using only my brand colors and fonts. Keep my wording where it is strong; flag any claim you could not trace to the text. Text: [paste]
What can go wrong?
- Feeding a full issue produces crowded slides; one idea per carousel works better.
- Check text size on a phone before posting.
Our take
Good advice hidden in a simple build: prove it manually before automating. He tried and failed several times before landing on a format, and recommends making two or three carousels by hand first. Wyndo saved his brand colors, fonts, spacing and voice notes once, so every carousel starts from the same spec instead of a fresh negotiation with the model. The structure is fixed too: a hook slide, a few supporting slides and a closing follow or subscribe slide. Feed it one idea from a newsletter, not a whole issue, or the slides get crowded. Rendering HTML, screenshotting each slide and combining them into a PDF is a little manual, which is why his advice to do two or three by hand before packaging it as a skill makes sense. Check text size on a phone before posting, since that is where most people will see it. Image-heavy designs still need a designer, and brands without agreed guidelines should settle those first.
Where the time goes back: The design wrestling that made carousels a two-hour job is replaced by a spec you write once.
FAQ
How long does it take?
Why HTML?
Source and credit
The original prompt on this page is by Wyndo, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- How I Built LinkedIn Carousels Using Claude Skills in Less Than 5 Minutes
- Creator
- Wyndo
- Published on
- aimaker.substack.com (Substack)
- Original date
- Jan 22, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.