When should you use it?
- You generate short-form video or image ads
- Outputs look generic
- Several accounts need consistent formats
Not for: Copying competitors' creative wholesale; Publishing without review
What do you need, and what do you get?
You need
- Example videos you like
- Brand rules
- Publishing accounts
You get
- Approved template library
- Drafts built from templates
- Review queue
How does it work, step by step?
- Collect examplesGather posts that performed well in your niche.
- Describe structureWrite each as a template: hook, beats, length, captions, music style.
- Approve by handOnly templates a person approves enter the library.
- Generate from templatesRequire the agent to cite the template it used.
- Review before postingA person approves every draft and records results per template.
The prompt
Our own prompt, inspired by u/tgdn on r/ClaudeAI and written to work in Claude Code, Claude and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Create a {length}-second video script for {product} using approved template {template_id}: {template}. Follow its hook and beat structure. Use only product facts from {facts}. Return script, shot list, captions, and the template ID used. Mark claims needing proof.
Inspired by u/tgdn on r/ClaudeAI: I let Claude Code run marketing for real brands - one video hit 5.3M views on Instagram. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Bad generations stay bad; reject rather than patch.
- Templates describe structure; do not reuse others' footage.
Our take
The author is candid that taste stays human and bad generations stay bad. The approved-template library is how that taste gets encoded so the agent can use it without reinventing structure each time. Add per-template result tracking so winners rise and weak templates retire. Collect examples carefully and respect copyright and platform rules when analyzing competitors. Approve every template by hand before it enters the library. Generate from templates, then review before posting. Do not auto-publish until the library has proven itself across several campaigns. Track spend on generation models separately from ad spend. Keep brand and legal claims on a deny list the agent cannot override. Refresh templates when platform formats change. Measure click and conversion by template, not only by campaign. Store rejected generations briefly so you can teach the scorer what bad looks like, then delete them. Have a second person spot-check new templates before they enter rotation for paid spend.
Where the time goes back: Fewer generic drafts reach review because the agent starts from formats you approved.
FAQ
Why a command-line tool?
Do templates kill creativity?
Source and credit
Inspired by u/tgdn on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I let Claude Code run marketing for real brands - one video hit 5.3M views on Instagram
- Creator
- u/tgdn on r/ClaudeAI
- Published on
- Original date
- Apr 10, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- 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 23, 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.