Browse / Content & marketing / slideshows-factory
slideshows-factory
bartubozkurt
Turn your website into a brand brief, and other people's viral slideshows into your own hooks.
Open bartubozkurt/slideshows-factory → Checked against the four rules.
agent-skillsai-agentsanthropicclaudeclaude-codecontent-marketingcopywritingcreator-toolsgrowth-marketingllmorganic-growthprompt-engineering
Built for Claude Code
ships .claude CLAUDE.md and nothing for other agents.
In its own words
A Claude Code workspace with 14 hook formulas, a self-critique pass, and hard guardrails against invented stats and marketing-speak. Text only, no image generation.
A Claude Code workspace that turns your website into a brand brief, and screenshots of TikTok slideshows into hooks, captions, and slide text for your own product.
Output is text only. It never generates, crops, or designs images. The deliverable is always words you type into a slideshow editor yourself, plus a plain description of what should be on each frame so you can go source it.
There is no code here. No install, no dependencies, no build step. It's a set of context files and skills that Claude Code reads.
Requirements
- Claude Code installed and logged in
- A website or store listing for your product (so
build-brandhas something to read)
Run
That's the whole setup. CLAUDE.md loads automatically every session.
The cd matters — Claude Code reads CLAUDE.md and .claude/skills/ from the directory you launch it in. Start it anywhere else and you get a plain Claude session with none of this loaded.
First session — build your brand file
Paste your URL and nothing else:
build-brand fires, reads your homepage plus up to 3 sub-pages, writes context/brand.md, and shows you the pain points it extracted.
Then correct those pain points by hand. They drive every hook you will ever generate, and a landing page describes features, not frustrations. Five minutes here is worth more than any prompt tweak.
Anything the skill inferred rather than read is marked [inferred] so you know where to look.
The repository's own description, then 19% of its README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.