Generate a cinematic ad open (3-shot intro)
The close-up → wide reveal pattern is the most reliable 'cinematic' structure.
by @whitney · recommended tool Freepik · 0 unlocks
0
You'll need
CLAUDE SKILLS
seedance-prompts
EXAMPLES · WHAT THIS PROMPT PRODUCES
Sample output
**3-shot cinematic opener (9s) — Halcyon mechanical watch** **Shot 1 (0–3s) — Extreme close-up, mystery.** Macro on the watch's escapement, the balance wheel oscillating in deep shadow. A single sliver of light rakes across the polished gear teeth; we don't yet know what we're looking at. Slow, almost imperceptible push-in. **Shot 2 (3–6s) — Medium, pulling wider.** The frame eases back to reveal the open caseback and the engraved rotor turning, then a wrist coming into focus — context arrives. A slow dolly-out introduces the watch on a wrist, cuff just visible. **Shot 3 (6–9s) — Wide hero reveal.** Full wide: a man lowering his sleeve in a dim study, the watch catching a clean key-light flash as his arm settles — the payoff. The Halcyon dial reads sharp and legible in the final beat. Consistent across all three: a cool desaturated steel-and-amber LUT, fine cinematic grain, and matched contrast so the cut feels like one continuous reveal rather than three clips. The close-up → wide pattern delivers the "premium film" feel reliably. Delivered 16:9 at 24fps, with a 9:16 reframe that keeps the escapement and the wrist centered.
PRICE HISTORY0 cr · current
PROMPT TEMPLATE · v1.0.0
3-shot cinematic opener, 9 seconds total. Shot 1 (0-3s): extreme close-up, mystery, reveal detail of <THING>. Shot 2 (3-6s): medium, pulling wider, introducing <SUBJECT/CONTEXT>. Shot 3 (6-9s): wide hero reveal, <PAYOFF_MOMENT>. Consistent palette, grain, and LUT across all 3.
WORKFLOW
- 01In Claude, invoke the seedance-prompts skill to draft the shot-by-shot prompt.
- 02Open Freepik and select the Seedance 2.0 model.
- 03Paste each shot, generate, and stitch in your editor.
RESULTS · WHAT PEOPLE GOT
0Sign in to show colleagues what this case produced.
No results posted yet. Used this case? Show colleagues what it produced.
DISCUSSION
0 commentsSign in to join the conversation.
No comments yet — be the first.
MORE LIKE THIS