The shot list, and the Claude skill behind it
The shot list, and the Claude skill behind it
Higgsfield Academy
Caption
Most people burn credits right here: open Seedance, type a prompt from scratch, hate the result, tweak it, run it again — twenty generations later the idea's a mess and the budget's gone. The fix is to never write the prompts by hand at all.
A skill does the writing for you
A skill is a file you load into Claude that teaches it one job, exactly your way. This one does a single thing: it writes shotlists with prompts tailored for Seedance 2.0. Everything learned making the last film — how Seedance wants a shot described, what holds character consistency, what breaks it — is packed into that one file, linked in the video description. Load it once, and Claude stops guessing and starts writing prompts the way you would.
Load the skill once and reuse it — that's what stops Claude from guessing on every ad you shotlist after this one.
Three things you hand it, every time
In a new chat, three inputs go in before Claude writes a single prompt:
The script
The whole ad, written out beforehand — scenes, beats, one clear idea per scene.
Every locked asset
Not described — uploaded straight from the canvas. The more Claude can see, the less generic it writes.
A name for each one
@hero, @headphones, @kitchen and so on — so the skill knows exactly which upload is which when it writes prompts.
Skipping the second one is the most common mistake — describing an asset in words instead of handing Claude the actual image is exactly why a generic prompt comes out generic.
The names you give Claude here aren't cosmetic — they're the same names you'll give these same assets as Elements inside Higgsfield a moment later. Two different steps, matched names on purpose, so everything lines up once you start generating.
What comes back isn't loose prompts — it's one shotlist
Claude hands back a full shotlist: a style block at the top, then every scene broken into prompts, each one written for Seedance. It's connected two ways that matter.
The block at the top is the style prefix — lighting, camera, color, the whole look — and it's glued to every single prompt in the document. Change it once, in one line of chat, and it changes everywhere at once.
Every prompt also has a name — 1a, 1b, 2a — so you can talk to Claude like an editor: edit prompt 1a, do this, and only that one prompt changes. Everything else stays locked.
That's the whole advantage over prompting one shot at a time. You're not juggling twenty loose chats — you're editing one connected document, and a fix to the style prefix or a single named prompt never touches the rest.