0:38
A 38 second vertical short for Northwind Coffee, a made-up roaster: six b-roll shots of a pour-over, with the words on screen from the script. Sour and thin means too coarse, bitter and dry means too fine.
Made with Claude Code · PlaybookExample output
Video
The finished short. Silent cut: you record the voiceover yourself. B-roll made from the playbook's own prompts for a made-up roaster, cut to its edit list.
Prompt Vertical 9:16. Matte black hand grinder in focus on a walnut counter, plain cream paper bag of coffee beans blurred in the near left foreground, eye level, space above. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Full prompt
Vertical 9:16. Matte black hand grinder in focus on a walnut counter, plain cream paper bag of coffee beans blurred in the near left foreground, eye level, space above. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Prompt Vertical 9:16. Close, slightly high side view: black dripper on a glass carafe, coarse grounds inside, a fast thick stream of coffee running into the carafe, walnut counter. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Full prompt
Vertical 9:16. Close, slightly high side view: black dripper on a glass carafe, coarse grounds inside, a fast thick stream of coffee running into the carafe, walnut counter. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Prompt Vertical 9:16. Close, slightly high side view: black dripper on a glass carafe, fine grounds inside with water pooled on top, a single drop falling below, walnut counter. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Full prompt
Vertical 9:16. Close, slightly high side view: black dripper on a glass carafe, fine grounds inside with water pooled on top, a single drop falling below, walnut counter. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Prompt Vertical 9:16. Eye level, close. Gooseneck kettle spout from top of frame pouring a thin stream into a black dripper on a matte black scale, display turned away, walnut counter. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Full prompt
Vertical 9:16. Eye level, close. Gooseneck kettle spout from top of frame pouring a thin stream into a black dripper on a matte black scale, display turned away, walnut counter. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Prompt Vertical 9:16. Eye level close up of fingers turning the plain dial of a matte black hand grinder, no numbers on the dial, walnut counter. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Full prompt
Vertical 9:16. Eye level close up of fingers turning the plain dial of a matte black hand grinder, no numbers on the dial, walnut counter. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Prompt Vertical 9:16. Eye level, cream ceramic cup of black coffee on a walnut table, steam rising, black dripper blurred behind, cup in the lower third with space above. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Full prompt
Vertical 9:16. Eye level, cream ceramic cup of black coffee on a walnut table, steam rising, black dripper blurred behind, cup in the lower third with space above. Soft side window light, cream, walnut and matte black, shallow 50mm focus, no faces, no text, no logos.
Made with Claude Code · PlaybookExample output
Image
Step 2: the b-roll stills. Made with GPT Image 2.5 from the six image prompts step 2 wrote, unedited. Beat 3 used beat 2 as a reference, as the step said.

Script: sour pour-over, fix your grindExample output

Script: sour pour-over, fix your grind

1. Hooks

Type	Hook	Words
Common mistake	Sour pour-over? Don't blame your beans.	6
Surprising fact	Sour coffee usually means the water ran through too fast.	10
Question	Does your pour-over taste sour even with good beans?	9

Recommended: the common mistake hook. It names your viewer's exact problem in two seconds, and a roaster saying "don't blame your beans" is unexpected enough to stop the scroll.

2. Script

About 38 seconds, 87 words. Every shot shows hands and gear only.

Beat	Seconds	Voiceover	On screen	B-roll
1	0 to 3	Sour pour-over? Don't blame your beans.	Sour? Don't blame the beans.	Top-down on the counter. A hand slides a bag of beans out of frame, leaving the grinder in the center.
2	3 to 10	It's usually your grind. Sour and thin means it's too coarse. The water runs through too fast.	Sour and thin = too coarse	Side-on close-up of the dripper. Water pours onto coarse grounds and streams straight through into the carafe.
3	10 to 14	Bitter and dry? Opposite problem. Your grind is too fine.	Bitter and dry = too fine	Same framing as beat 2, now with fine grounds. Water sits on top and drips slowly.
4	14 to 27	Here's how to check. Our recipe is 15 grams of coffee to 250 grams of water. The whole brew should take two and a half to three and a half minutes.	Brew time: 2:30 to 3:30	Scale display as beans pour in, stopping at 15 g. Cut to water pouring until the scale reads 250 g, with a timer running beside it.
5	27 to 33	Done in under two minutes? Grind finer. Change one notch at a time.	Under 2:00? One notch finer.	Timer stopping before 2:00. Cut to fingers turning the grinder one click finer.
6	33 to 38	Save this for the next time your pour-over tastes sour.	Save for your next sour cup	Slow pour from the carafe into a cup, steam rising. Hold on the cup while the text sits on screen.

Everything in the script comes from your notes, so there are no [ask:] gaps.

3. End line

"Save this for the next time your pour-over tastes sour."

Sour cups keep happening, so this gives people a reason to keep the video as a fix they'll come back to.

Made with Claude Code · Playbook

Markdown · Document

Step 1: hooks and script. Three hooks, then the script in six beats with the words on screen and the shot for each.

MarkdownVoiceover readExample output
Voiceover read
Sour pour-over? / Don't blame your beans. [3 s]

It's usually your grind. / Sour and thin / means it's too coarse. / The water runs through too fast. [7 s]

Bitter and dry? / Opposite problem. / Your grind is too fine. [4 s]

Here's how to check. / Our recipe is 15 grams of coffee / to 250 grams of water. / The whole brew should take / two and a half to three and a half minutes. [13 s]

Done in under two minutes? / Grind finer. / Change one notch at a time. [6 s]

Save this / for the next time your pour-over tastes sour. [5 s]

Total read time: about 38 seconds at a calm pace, pauses included. That's 87 words, comfortably inside your 30 to 45 second window.
Made with Claude Code · Playbook
Markdown · Document
Step 3: the voiceover read. Pauses and stress marked, with the seconds for each line, ready to record on a phone.

Post captionsExample output

Post captions

TikTok

Pour-over tasting sour? It's usually the grind, not the beans. Done in under 2 minutes? Go one notch finer. #pourover #grindsize #homecoffee

140 characters.

Instagram Reels

Sour and thin? Your grind is too coarse. Bitter and dry? Too fine. Our recipe is 15 g coffee to 250 g water. The whole brew should take 2:30 to 3:30. Under 2 minutes? Go one notch finer.
Save this for the next time your pour-over tastes sour.
#pourover #grindsize #homecoffee

275 characters.

YouTube Shorts

Title

Sour pour-over? Fix your grind, not your beans

46 characters.

Description

Sour and thin means your grind is too coarse: with 15 g of coffee to 250 g of water, aim for a 2:30 to 3:30 brew and go one notch finer if it finishes in under 2 minutes.

Made with Claude Code · Playbook

Markdown · Document

Step 4: post captions. One caption each for TikTok, Instagram Reels and YouTube Shorts.

Edit list and export settingsExample output

Edit list and export settings

Edit list

Beat	Clip	Start	End	Words on screen	Cut lands on
1	Grinder push in, bean bag passes out of frame	0:00	0:03	Sour? Don't blame the beans.	Frame 1, on "Sour"
2	Coarse grounds, fast stream into the carafe	0:03	0:10	Sour and thin = too coarse	"It's" in "It's usually your grind"
3	Fine grounds, water pooled on top, slow drip	0:10	0:14	Bitter and dry = too fine	"Bitter"
4	Kettle pour, tilt down to the dripper	0:14	0:27	Brew time: 2:30 to 3:30 (comes in on "whole")	"Here's"
5	Fingers turn the grinder dial one click	0:27	0:33	Under 2:00? One notch finer.	"Done"
6	Steaming cup, pull back	0:33	0:38	Save for your next sour cup	"Save"

Placing the cuts

The times are the targets from the read. Once you've recorded, move each cut to the first frame of the word in the last column. That way the pause before each line stays on the outgoing clip and the new clip arrives with the word.
Clip 1: trim the first half second or so off the generated clip. Most image-to-video clips ease in from a standstill, so this keeps the push in moving from frame 1. Start the voiceover on frame 1 too, with no silent lead-in.
Clip 4: this one has to fill 13 seconds. If your tool tops out at 10, slow the clip to fit instead of looping it, because the jump at a loop point is easy to spot. Bring the beat 4 text in on "whole" so the times appear when they're spoken, not during the grams.
Clip 6: the voiceover ends at about 0:37. Hold the cup for the last second so the save text can be read before the video ends.

Export settings

Aspect ratio: 9:16
Resolution: 1080 by 1920
Frame rate: 30 frames per second. Set the timeline to this before you add clips.
Length: 0:38
File: MP4 with H.264 video and AAC audio at 48 kHz. TikTok, Instagram and YouTube all accept this.

Made with Claude Code · Playbook

Markdown · Document

Step 5: the edit list. The cut list the short above was edited to.

Works with

Claude
Claude Code
ChatGPT
Gemini
Cursor
+24 more
+22 more

Not affiliated with or endorsed by the companies shown.

Content and socialPlaybookMembers

Make faceless short-form videos with AI

Turn one idea into a 30 to 45 second vertical video with script, b-roll, voiceover and captions. No face.

Version 1.0Updated 12 Oct 2026

Included with membership: 10 systems, 21 parts

Membership also includes Launch a one-page site with your AI in an hour and Build a brand kit in an afternoon.

Needs access to: None
Permissions: None
Time to result (our estimate): 10 minutes to set up, 60 minutes a run

Example

Example session

Step 1: Write the script
You
Pasted the step 1 prompt: faceless shorts for TikTok, Reels and Shorts about better coffee at home, with today's idea that sour pour-over usually means the grind, not the beans.
Your AI
Recommended: the common mistake hook. It names your viewer's exact problem in two seconds, and a roaster saying "don't blame your beans" is unexpected enough to stop the scroll.
Step 2: Plan the b-roll
You
Pasted the step 2 prompt.
Your AI
Look: Soft side window light, a palette of cream, walnut and matte black, and shallow 50mm focus with a softly blurred background.
Steps 3 to 5: Voiceover, captions and edit list
You
Pasted the step 3, 4 and 5 prompts, one at a time.
Your AI
Total read time: about 38 seconds at a calm pace, pauses included. That's 87 words, comfortably inside your 30 to 45 second window.

A hand grinder on a walnut counter with the words: Sour? Don't blame the beans. — What comes out

Fit

About this item

Pick one idea and finish with everything a faceless short needs: a script written in beats, b-roll prompts that all share one look, a voiceover read you can record on your phone, captions for each platform and an edit list that tells you where every cut goes.

Most of it happens in one Claude chat. The edit is yours, in CapCut on your phone or any editor you know, with an optional desktop route through Hyperframes for Claude Code users.

What you get

Three hooks and a script split into beats, with words on screen
Image and motion prompts for every beat in one consistent look
A voiceover read with pauses and stress marked
Post captions for TikTok, Instagram Reels and YouTube Shorts
An edit list with clip lengths and cut points

Good fit

Creators and small businesses who want to post short video without being on camera
Turning one point from a long video into a short

Not for

Talking head videos
Ads that need a product shown exactly as it is

Who it is for

Skill level: Use AI weekly

How to use

The steps

Step 1: Write the script
Writes three hooks and a 30 to 45 second script in beats, each with the voiceover line, the words on screen and the b-roll shot.
Runs in Claude
Step 2: Plan the b-roll
Turns each shot into an image prompt and a motion prompt in one consistent look, plus stock search terms.
Runs in Claude
Step 3: Prepare the voiceover
Marks pauses, stress and timing on the script so you can record it on your phone in a few takes.
Runs in Claude
Step 4: Write the post captions
Writes a caption for TikTok, Instagram Reels and YouTube Shorts from the script.
Runs in Claude
Step 5: Make the edit list
Lays out every clip, its length, the words on screen and where each cut lands, ready for CapCut or any editor.
Runs in Claude
Step 6: Render with HyperframesOptional
For Claude Code users, builds a reusable vertical template from the edit list and renders the MP4.
Runs in Claude Code

How to use it

Download the playbook and open README.md. Each step says which tool it runs in.

Trust

What's inside

01-script.md1.1 KB
02-b-roll.md844 B
03-voiceover.md346 B
04-post-captions.md533 B
05-edit-list.md406 B
06-render-with-hyperframes.md1.2 KB
README.md2.9 KB

File names and sizes only. The files come with membership.

Permissions required

None

Requirements

You bring

One idea, with any facts or numbers you want in the video
An image tool for b-roll, or a free stock footage site
Your phone to record the voiceover, and CapCut (www.capcut.com, free, paid extras) or another editor
Optional render step: Hyperframes (github.com/heygen-com/hyperframes, Apache-2.0, free), Node 22+ and FFmpeg

Outside costs

Image or video generation credits, if you generate the b-roll: Varies by tool (our estimate)

Tested on

VerifiedTested in the last 90 days

Claude Code · Claude Opus 5.512 Oct 2026 · Steps 1 to 5. Stills from the step 2 prompts with GPT Image 2.5, clips with Kling 3.0, cut to the step 5 edit list. Step 6 not run.

Known limitations

It writes the script and every prompt. Making the clips and editing them happen in your own tools.
It does not record or clone a voice. You record the voiceover, or use a text to speech tool you choose.
AI video tools still struggle with hands and readable text, so the shot plan avoids both where it can.
The optional Hyperframes render step was not part of our test run. Its commands come from the Hyperframes project's own page.

Plan a week of posts and hooks from one idea

Example output

Week of 12 October

Day	Hook	Status
Mon	We stopped posting every day. Then our numbers went up.	Idea
Tue	Posting less is not lazy. It is a strategy.	Idea
Wed	Why posting less made our content work harder	Idea
Thu	Daily posting was costing us more than time.	Idea
Fri	What our content week looks like now we post less	Idea
Sat	This week: why fewer posts worked better for us	Idea
Sun	None	Idea

Made with Claude · Template

Template, Members

Clean up any transcript so it reads like an article
MarkdownExample output
How we plan a month of content in one afternoon
Source: YouTube auto-captions copied from Show transcript, about 5 minutes, one speaker. [Music] tags removed. No unclear passages.
Why we stopped posting every day (00:04)

Hi, welcome back. So today I want to talk about how we plan a month of content in one afternoon, because for a long time we didn't do it that way at all.

So for about a year we posted every single day. Every single day. And by the end of it, nobody on the team wanted to open the content calendar. Nobody.

And the posts got worse, not better, which is the opposite of what you'd expect, right? You'd think practice makes it better. But we were making content to fill a slot, not

One video a month (00:48)

So we changed one thing. Just one thing. Now we record one long video at the start of each month, and everything else comes

Pe
Made with Claude · Skill
Skill, Members
Works with Claude, Claude Code, ChatGPT and 18 more
Turn one video into a week of posts
InstagramExample output
Say the point first
acmestudio
Before every answer on camera, we say the point in one sentence. Then we explain it. That sentence can be lifted straight out as a post. And if we can't get the idea into one sentence, it isn't ready yet, so we park it until next month. Save this for the next time you record.
Made with Claude · Playbook
Playbook, Members
Works with Claude, Claude Code, ChatGPT and 18 more

Questions

Do I have to generate the b-roll with AI?: No. Every beat also comes with two stock footage search terms, so you can use free stock clips or film the shots yourself on your phone.
Why record the voiceover myself?: Your voice is what makes a faceless channel recognisably yours, and a phone in a quiet room is good enough. If you prefer text to speech, the read from step 3 works there too.
Do I need Claude Code?: No. Steps 1 to 5 run in Claude chat on your phone or computer, with CapCut for the edit. Step 6 is an optional desktop route for people who already use Claude Code.
Is Hyperframes included?: No. It is an open-source tool by HeyGen that you install from its own page if you want it. We link to the source and never bundle it.

Make faceless short-form videos with AI

Example

Example session

Fit

About this item

What you get

Good fit

Not for

Who it is for

How to use

The steps

How to use it

Trust

What's inside

Permissions required

Requirements

You bring

Outside costs

Tested on

Known limitations

More

Related items

Plan a week of posts and hooks from one idea

Clean up any transcript so it reads like an article

Turn one video into a week of posts

Questions