The argument in one line.
Generic AI carousels come from generic prompts -- giving Claude a design system converted from a real visual reference is the single change that makes every output look intentional and on-brand.
Read if. Skip if.
- You are posting AI-generated carousels on Instagram and they all look like each other and nothing like your brand.
- You use Claude regularly and want to stop re-explaining your aesthetic every session.
- You want a repeatable content workflow where one slash-command produces a full carousel from a topic.
- You are comfortable with Claude chat and ready to take one step into Claude Code.
- You already have a polished design system and a mature image-generation workflow.
- You are not creating social content and have no interest in Instagram carousels.
The full version, fast.
The problem with AI carousels is that everyone uses the same vague prompts and gets the same generic output. The fix is a design system -- a color palette, type hierarchy, and layout rules extracted from a real visual reference -- stored as a markdown file that Claude can read. One screenshot of a Pinterest design you like, one prompt to Claude chat, and you have a design system. Connect Higgsfield via MCP for image generation, drop your design system MD into the project folder, and Claude Code will translate it into precise image prompts automatically. Encode the full workflow as a Claude Code skill and you reduce carousel creation to a single slash command plus a topic.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · The problem: they all look the same
Hook stating that AI carousels are generic because prompts are generic. Before/after teaser.

02 · Why they look the same + the fix
Claude needs references, not vague prompts. The solution is a design system from a real reference.

03 · Find design references on Pinterest
Search graphic design on Pinterest, find a style you want to clone.

04 · Build a design system with one prompt
Screenshot the reference, drop into Claude chat with the prompt: turn this into a design system in an HTML file and a design MD file.

05 · Design system + MD file walkthrough
Claude generates HTML design system and MD file. Explains what a design MD file is. Download all.

06 · Extend beyond carousels + Claude Code setup
Design system reusable for landing pages, emails. Switch to Claude Code, open project folder.

07 · Connect Higgsfield MCP
Go to higgsfield.ai/mcp, add as custom connector in Claude Code settings, sign in, set always-allow.

08 · Test the design system with Higgsfield
Unzip design system into project folder. Prompt Claude Code to generate an image from the design system. Claude reads the MD file and writes the image prompt automatically.

09 · Viral carousel structure framework
Hook, Pain, Steps, Result, CTA -- five-slide structure that converts.

10 · Create and run the Aurora Carousel Skill
Paste skill-creation prompt into Claude Code. Skill saved as /aurora. Restart Claude, invoke with /aurora + topic. Skill asks onboarding questions first run, bakes answers in.

11 · Full carousel output + schedule with Blotato
Complete carousel generated: all slides, caption, LinkedIn post. Blotato for scheduling.

12 · Outro + CTA
Final community push at $9. Subscribe CTA.
Lines worth screenshotting.
- The reason AI carousels all look the same is that everyone uses the same prompt -- not because AI cannot produce variety.
- One screenshot from Pinterest plus a single prompt to Claude chat is the entire first step toward a branded design system.
- A design MD file converts visual decisions into language Claude can read -- color values, type hierarchy, spacing rules, component behavior.
- Once a design system exists, it works for more than carousels -- landing pages, emails, and newsletters can all pull from the same file.
- Claude Code reads files in the open project folder by default; putting your design MD there requires zero extra setup.
- MCPs let Claude Code call Higgsfield directly -- you describe what you want in plain English and Claude writes the actual image prompt itself.
- The carousel structure that works: Hook, Pain, Steps, Result, CTA -- five slides, one purpose each.
- A Claude Code skill is just a written-down set of steps; once saved, a slash command runs the full workflow on any topic without re-explaining anything.
- Skills can ask onboarding questions the first time and bake the answers in so they never ask again.
- Blotato connects the output directly to a scheduling queue -- caption, LinkedIn post, and Instagram slot are all generated with the carousel.
- The host positions the community as the actual product; the tutorial is the proof-of-concept that earns the click.
One file that makes every Claude output consistent.
Giving Claude a design system in plain text -- not a vague style description -- is what separates outputs that look intentional from outputs that look generated.
- A design system does not have to be hand-crafted. One screenshot of something you like and one prompt to Claude chat produces a complete color palette, type hierarchy, and layout rules in minutes.
- The markdown version of a design system is the file that actually matters for consistency. Claude reads it at the start of every session and applies the same rules without being re-briefed.
- MCPs eliminate the copy-paste step. When Claude Code connects to an image generator directly, it writes the image prompt itself based on your design system -- you describe the subject, Claude handles the translation.
- Skills turn a multi-step process into a single invocation. Any workflow you repeat more than twice is worth encoding as a slash command so the steps never drift and the output never varies.
- The carousel structure that earns follows is sequential: hook the viewer, name their pain, show the steps, prove the result, then ask for an action. Each slide has one job and no more.
- Onboarding questions on first run are a feature, not friction. Baking the answers into a skill means the tool knows your audience, your offer, and your voice without you repeating it.
Terms worth knowing.
- Design system
- A documented set of visual rules -- colors, type scales, spacing, component behavior -- that enforces consistency across every piece of output. Here it is generated by Claude from a single screenshot.
- Design MD file
- A markdown version of a design system written in language Claude can parse. It is the actual input you give Claude Code so it applies the right style without being re-briefed each session.
- MCP (Model Context Protocol)
- A standard that lets Claude Code talk directly to external services like Higgsfield. Once connected, Claude can call the service as a tool and pass structured prompts without the user visiting the external site.
- Higgsfield
- An AI image and video generation platform with an MCP connector that lets Claude Code generate on-brand visuals by sending it a prompt automatically derived from your design system.
- Skill (Claude Code)
- A saved set of step-by-step instructions stored in your Claude Code project. Invoked with a slash command, it runs the same workflow every time on whatever input you provide.
- Blotato
- A third-party scheduling service that can auto-post generated carousels and captions to Instagram and LinkedIn on a set schedule.
Things they pointed at.
Lines you could clip.
“Claude works so much better when you have references.”
“Turn this into a design system in an HTML file and a design MD file. That is it.”
“I could not write this prompt if I tried.”
“A skill is just: you write down the steps for Claude to follow, it goes ahead and follows them so you get the same result every single time.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
Generic AI carousels have a tell: they look like every other generic AI carousel. Duncan Rogoff, a former art director for Apple and PlayStation who now runs an AI agency, opens by naming the problem before the title card fades -- and then spends eleven minutes solving it with one screenshot, one markdown file, and a slash command.
Named ideas worth stealing.
Hook, Pain, Steps, Result, Join
- Hook (cover slide, grab attention)
- Pain (name the problem directly)
- Steps (numbered list, what to do)
- Result (specific outcome from following the steps)
- Join/CTA (comment keyword, join offer, etc.)
Five-slide carousel structure. Each slide has one job.
Design System pipeline
Screenshot a visual reference, one Claude chat prompt, Claude outputs HTML design system plus MD file, give the MD to Claude Code, get consistent branded outputs every session.
How they asked for the click.
“If you wanna get access to anything we build today along with tons of done for you prompts and skills for Claude Code, just check the link in the description. You can get started today for only $9.”
Pitched twice at natural transition points. Before/After GUESSING vs BUILDING visual shown on screen during second pitch. Low price point removes friction.




































































