Scroll for 10 seconds and you can spot it. The same yellow word by word captions. The same whoosh on every cut. The same zoom punch on the 3rd word. Editing tools got cheap and smart, so every edit started to look the same.
Premium is not more effects. Premium is decisions. Where you cut, how long you hold a shot, what goes on screen and what you leave out. The creators you recognize in 1 second make the same decisions every time, on purpose.
That is where Claude comes in. Not as an editor dragging pieces around a timeline, but as the brain that writes your rules down, plans every cut before you open the app, and holds you to your own taste.
The editor's brain: decide before you cut
01Write an edit style bible once, reuse it forever
The secret. Your style is not a vibe. It is a list of rules. Write it down once.
Why it works. Generic edits happen when you decide everything from scratch each time, which means you end up picking whatever the app suggests. A written bible makes your choices repeatable: cut rhythm, the transitions you allow, text style, sound cues, the things you never do.
Role: You are a senior video editor who builds style guides for creators.
Goal: Write my personal edit style bible from my best work.
Context: I make [type of content] for [audience] on [platform].
My 3 best videos, as transcripts with shot notes: [paste].
Creators whose edits I admire and exactly what I like: [list].
Things I hate seeing in edits: [list].
Output format:
1) Rhythm: average shot length, when I hold longer, when I speed up
2) Cuts and transitions I allow (max 4) and ones I ban
3) On screen text: feel of the font, position, max words per line, when text appears
4) Sound: music energy, sound effects I allow, where I use silence
5) Color and framing notes
6) 5 "never" rules
7) A 10 line checklist I run before every export
Be specific. If my examples contradict each other, point it out and ask me to choose.02Turn the transcript into a cut list before you open the editor
The secret. Edit on paper first. Most of a premium edit is decided in the transcript.
Why it works. Scrubbing footage eats hours, and you keep weak takes because you got attached to them. Claude reads the whole transcript in seconds and is attached to nothing. Grab a transcript with timestamps from your editing app's auto captions or any transcription tool.
Role: You are my story editor. Follow my edit style bible: [paste, or "it is in the Project instructions"].
Goal: Turn this raw transcript into a cut list for a [length] second video.
Context: Transcript with timestamps: [paste]. The one idea this video must land: [one sentence]. Audience: [who].
Output format: a table with columns
Keep (start to end timestamp) | Line | Why it stays | Visual or B roll idea | On screen text (if any)
Then:
1) Lines you cut and why (one line each)
2) Repeated takes: which take is best and why
3) Estimated total runtime
Never rewrite my spoken words. Only choose, order and trim them.03Draw a pacing map, not just a sequence
The secret. Pace has a shape. Plan where the energy rises, drops and resets.
Why it works. Flat pacing is the most common AI look: 40 seconds of cuts at the same speed. Retention lives in contrast. A pacing map shows you where to speed up, where to let a shot breathe, and where to kill the music for 1 beat.
Role: You are an editor who plans rhythm before cutting.
Goal: Build a pacing map for this cut list.
Context: Cut list: [paste]. Platform: [Reels / TikTok / YouTube]. My rhythm rules: [from the bible].
Output format: a map in blocks of 3 to 5 seconds:
Time | Energy (1 to 5) | Shot length | Cut type | Music or SFX move | Text on screen
Then mark the 2 places viewers are most likely to drop off and what to change there.
Rule: never more than 2 blocks in a row at the same energy level.04Engineer the first 3 seconds
The secret. The first 3 seconds have 3 jobs: stop the thumb, promise something, and open a question the viewer needs answered.
Why it works. People decide in the first second. Generic hooks like "Here are 3 tips" are exactly what every AI prompt spits out, so viewers read them as noise. Your hook has to be built from your own footage.
No footage, no audience, no style. Claude gives you the average hook of the internet, which is the generic look you are trying to escape.
Role: You are a retention editor for short vertical video.
Goal: Design 5 options for the first 3 seconds of this video.
Context: Cut list: [paste]. My strongest shot: [describe it]. My strongest line: [quote from transcript]. Audience and their problem: [ ]. My bible's text rules: [ ].
For each option give:
1) Frame zero: what is on screen before a word is said
2) First spoken line (must come from my transcript, or be marked NEW if I would need to record it)
3) On screen text, max 6 words
4) Sound at second zero
5) The open question the viewer now needs answered
Then rank them by how much they feel like my bible, not by how viral they are.
Avoid: "here are X tips", "you won't believe", "stop scrolling".Your voice on screen
05Captions that sound like you, not like a caption app
The secret. Captions are design and copy at the same time. Edit them, don't just transcribe them.
Why it works. Auto captions treat every word the same. Premium captions make choices: which word to emphasize, where to break the line, what to drop. Claude can mark all of that from your transcript and your rules.
Role: You are my caption editor. Follow my bible's text rules: [paste].
Goal: Turn this transcript segment into caption lines I can import into my editor.
Context: Segment with timestamps: [paste]. Max words per line: [3 or 4]. Language: [ ].
Output format: SRT, then a separate list of:
1) Words to emphasize (max 1 per line) and why
2) Filler words removed from captions but kept in the audio
3) 3 lines of on screen text that add meaning instead of repeating what I say
Keep my slang and my word choices. Do not make me sound more formal.06Pick 3 signature moves and repeat them every time
The secret. Recognizable creators don't use more effects. They use fewer, and they use them every single time.
Why it works. Recall comes from repetition. Pick 3 moves (1 transition, 1 sound cue, 1 text behavior) and put them in every video. Claude helps you choose moves that fit your content, then checks every cut list for them.
Role: You are a creative director shaping a creator's edit identity.
Goal: Propose signature moves I can repeat in every video.
Context: My bible: [paste]. My content: [ ]. What everyone in my niche already does: [list].
Output format:
1) 6 candidate moves (transition, sound cue, text behavior, framing habit), each with what it is, when it triggers, and why it fits me
2) The 3 to keep, and why
3) For each kept move: how to build it in [my editing app] in plain steps. Only describe features you are sure exist. Say "check in your app" when you are not sure.
Exclude anything my niche already overuses.Claude Code: the operator for repeatable work
Everything so far happens in chat. When the same job repeats every week, like cutting dead air, burning in captions or exporting 3 formats, Claude Code can do it on your computer with real tools. Claude Code is Anthropic's tool that works in your terminal: it writes and runs commands, and asks for your approval before it acts.
07Let Claude Code run ffmpeg for the boring, repeatable cuts
The secret. Automate what is the same every time, so your hands are free for what is different.
Why it works. Removing dead air, burning in captions and exporting 9:16, 1:1 and 16:9 versions are rules, not taste. ffmpeg is a free command line tool that does all of it, and Claude Code writes and runs the commands for you. Nothing runs until you approve it.
Put your raw files in 1 folder and open Claude Code inside it.
Say what you want in plain words, using the prompt below.
Read the commands, approve, check the result. Then save the script so next week it is 1 command.
Role: You are my post production assistant working in this folder.
Goal: Build a repeatable script for my weekly video prep.
Context: Raw files are in ./raw. Captions (SRT) are in ./captions with matching names.
Tasks:
1) Detect silences longer than 0.6 seconds and cut them, keeping 0.15 seconds of padding
2) Burn in captions using the font and size in ./style/captions.txt
3) Export a 1080x1920 (9:16) and a 1080x1080 (1:1) version to ./export
Rules: Never overwrite anything in ./raw. Show me the plan and the commands before running anything. Test on one file first and tell me what to check.
Save it all as a script I can rerun next week with one command.08Use Remotion when your style has to be pixel exact
The secret. If your captions or intro are part of your brand, turn them into code.
Why it works. Remotion is a framework for making videos with React code. Claude Code can write a Remotion composition straight from your bible (fonts, colors, the timing of each word pop) and render it the same way every time. Your brand stops depending on how carefully you clicked that day.
Role: You are a Remotion developer working in this project folder.
Goal: Build a reusable caption component that matches my edit style bible.
Context: Bible text rules: [paste]. Brand colors: [hex codes]. Font: [name, file in ./fonts]. Captions: ./captions/video01.srt. Video: ./raw/video01.mp4, 1080x1920.
Output:
1) A composition that plays my video with captions on top, max [3] words per line, emphasized words in [color]
2) Props so I can swap the video and SRT file without touching code
3) The render command
Before writing code, look at what is already in the project and explain your plan in 5 lines.Finish like a pro
09Let Claude attack your edit before your audience does
The secret. The last pass is not polish. It is an attack.
Why it works. You have watched your edit 40 times, so you can't see it anymore. In chat Claude can't watch the video, but it can judge a precise description: your final cut list with timings, the transcript, the text on screen. In Claude Code it can also pull still frames with ffmpeg and look at them, to check framing, text placement and visual repetition.
Role: You are a harsh senior editor reviewing a creator's final cut. Do not be polite.
Goal: Find everything that makes this edit look generic or lose viewers.
Context: My bible: [paste]. Final edit, block by block (time | on screen | what is said | text | sound): [paste]. Platform: [ ].
Output format:
1) The 3 moments viewers most likely leave, each with the exact fix
2) Every place I broke my own bible
3) Anything that looks like a default template or a trend everyone uses
4) One cut that would make it 10% shorter and better
Do not praise anything. If something works, skip it.Your weekly edit checklist
Quick summary
- Claude is your editor's brain and operator, not your timeline.
- Style is written rules. Keep your bible in a Claude Project.
- Decide in the transcript: cut list, pacing map, hooks.
- Edited captions and 3 signature moves give you a recognizable voice.
- Repeatable work goes to Claude Code with ffmpeg and Remotion.
- Always run a critique pass before you export.
