agentleFS
kaiyiwongkaiyiwong/skills/skills/genai/shot-planning/SKILL.md

shot-planning

Skill0 starsChanged 52 days agoMITView on GitHub

Plan a music video or short film from the song or story down to shots: a video bible (governing rule, act grammar, section jobs), a 9-panel beat board of key moments, a timed shot list, and prompts for 3×3 photographic storyboard sheets. Use whenever the user wants to plan, structure or storyboard a music video, MV, film or ad; asks for a shot list, beat board, storyboard, key moments, key frames, "what should happen in each section", or pastes lyrics or timecodes and asks what the video should show. Casual phrasings count: "give me the next 9 panels", "plan the shots for act 1", "this feels dull", "what happens in the chorus". Uses the photo-direction skill's rules for every panel and frame it writes.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. mojomast/open-higgsfield-skills★ 8same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 16 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the photo-direction skill before writing any panel or frame prompt: its writing rules, contradiction check and gotchas apply to every …

    line 22
  2. Distinctive:

    Default order: bible → beat board → shot list → storyboard → key frames (the beat board panels made final first.

    line 36
  3. Distinctive:

    Keep it to one screen. It is the thing that stops the video from being a straight story told with ordinary shots.

    line 48
  4. Distinctive:

    Every instrumental gap longer than ~4 s gets a job.

    line 52
  5. Distinctive:

    Performance plan: Prefer movement, stillness, gaze and a small recurring gesture vocabulary (4–6 gestures) over lip-sync.

    line 63
  6. Distinctive:

    If acts use different aspect ratios, state it per panel.

    line 78
  7. Distinctive:

    Every section contains at least one P or R shot.

    line 89
  8. Distinctive:

    No two neighbouring shots share the same size and angle.

    line 90
  9. Distinctive:

    Leave clean space for titles where needed (intro, end).

    line 97
  10. Distinctive:

    After the table, list what changed from the previous version in one line each.

    line 103
  11. Distinctive:

    Every sheet repeats the full World, Character and Look blocks, even when unchanged, so sheets match each other.

    line 113
  12. Distinctive:

    Flow: do neighbouring panels vary in size and angle.

    line 124
  13. Distinctive:

    Screen direction: do profile and walking directions agree across panels?

    line 125
  14. Distinctive:

    Don't regenerate a storyboard for small errors.

    line 129
  15. Distinctive:

    "Facing camera-left" still flipped: Write profile direction as a visible position.

    line 161
  16. Distinctive:

    Copies walking beside her read as a girl group,: not as being followed. State formation positions relative to her ("she in front, the …

    line 162

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Shot Planning

Turns a song (or story) into a plan for images: first the rules the video runs on, then the nine moments that carry it, then every shot with its time, then storyboard sheets to check the flow before final frames are made. The output is planning tables and image-generation prompts; this skill doesn't generate images itself.

Read the photo-direction skill before writing any panel or frame prompt: its writing rules, contradiction check and gotchas apply to every panel here.


Step 1: Pick the mode

ModeNeedsProduces
BibleSong timing, conceptSong map, layers, governing rule, act grammar, section jobs
Beat boardBibleOne 3×3 sheet: the 9 key moments, start to finish
Shot listBible (+ beat board if it exists)Timed shot table, tagged by layer
StoryboardShot list + a range ("shots 9–17")One 3×3 sheet prompt per 9 shots

Default order: bible → beat board → shot list → storyboard → key frames (the beat board panels made final first; everything else is built around them). Each mode can run on its own if its inputs exist. If the bible is missing, write it first in a short form and say so.

Gather only what's missing: lyrics with timecodes, the concept or story, the acts or locations, the character block(s) from photo-direction, and the project's Look block.


Step 2: Bible

Keep it to one screen. It is the thing that stops the video from being a straight story told with ordinary shots.

  1. Song map. Sections with start and end times. Check transcriptions (see Gotchas). Every instrumental gap longer than ~4 s gets a job.
  2. Layers. Name what runs alongside the story: performance (singing, movement, gesture vocabulary), choreography or ritual, and moments that could only happen in a music video. A plan with only a story layer is the most common failure.
  3. Governing rule. One reality-breaking rule, tied to the song's idea. Schedule it: set up in the intro → bent in the verses → broken hardest in the choruses → changed or reversed in the bridge → dropped or resolved at the end. Every effect must connect to the rule. Don't spend the best image in the intro.
  4. Act grammar. Each act gets its own way of filming (for example: ritual and locked symmetry → solo performance in an impossible space → loose, un-authored naturalism). The change of grammar tells the story as much as the events do.
  5. Performance plan. Prefer movement, stillness, gaze and a small recurring gesture vocabulary (4–6 gestures) over lip-sync. List any lip-sync shots explicitly; keep them rare, face-on, and placed where they mean something.
  6. Section jobs. A table: section | time | rule state | key moment. Each section must show something the previous one didn't.

Step 3: Beat board

Nine key moments from start to finish on one 3×3 sheet. Pick them from the section jobs: the opening image, the first sign of the rule, each chorus peak, the bridge change, the final image, and the thumbnail image. Write the prompt from references/sheet-templates.md.

If acts use different aspect ratios, state it per panel. Expect the model to ignore pillarbox bars; crop in the edit and generate those shots at their native ratio later.


Step 4: Shot list

A table per act: # | time | lyric or section | layer | shot | what happens. Layer tags: S story, P performance, R rule-break, C choreography.

Rules:

  • Every section contains at least one P or R shot.
  • No two neighbouring shots share the same size and angle. A setup may repeat only when repetition is the point; mark it ("same frame as 4, on purpose").
  • Name the master setups (a wide, a medium, a close-up) that most shots are generated from by editing, and say which shots use each.
  • Include angles the act doesn't have yet: low, overhead, behind, through glass or reflections, inserts of hands and objects, tracking.
  • Plan light or set changes across sections so the act visibly builds.
  • Leave clean space for titles where needed (intro, end).
  • Aim for 3–5 s per shot; AI video clips generate at 5–10 s, so trimming is easier than stretching.
  • Flag faces-in-crowds risks and plan around them (crop, shadow, or make sameness the rule).

After the table, list what changed from the previous version in one line each.


Step 5: Storyboard sheets

Nine shots per sheet in shot-list order; fill unused panels with solid black. Write one prompt per sheet from references/sheet-templates.md, each in its own code block, with the time range and lyric range as a heading above it.

Every sheet repeats the full World, Character and Look blocks, even when unchanged, so sheets match each other. When a sheet spans two locations, give a World block per panel range. Panel lines are one or two sentences of visible states, with profile direction written as a physical position ("nose pointing toward the left edge of the frame").


Step 6: Review a returned sheet

Judge the sheet as a storyboard, not as final frames:

  1. Flow: do neighbouring panels vary in size and angle; does the section build?
  2. Screen direction: do profile and walking directions agree across panels?
  3. Rule: can you see the governing rule's state change panel to panel?
  4. Continuity: character marks, wardrobe, world dressing.

Don't regenerate a storyboard for small errors; note the fix for the final frame. Call out decisions the sheet forces (an unplanned prop, a changed dressing) so they're locked once. Say plainly when a sheet is dull, and why (repeated setups, no change of state).


Output

  • Bible and shot lists as tables in the reply.
  • Sheet prompts in code blocks, one per sheet, in the order they'll be generated.
  • A short check list after each prompt: the 2–3 panels most likely to fail and what to look for.

Gotchas

  • A lyric-by-lyric shot list made a dull video. 51 shots of a straight story, the same two setups repeated, one light state for 1:48, and one expression throughout. The fix was structural: layers, a governing rule on a schedule, act grammar, section jobs. Write the bible before the shot list.
  • Grid maths. A 3×2 grid of 16:9 panels on a 3:2 sheet came back square. Sheet ratio = (columns × panel width) : (rows × panel height); 3×3 of 16:9 fits a 16:9 sheet. Set it in the platform's aspect-ratio setting too.
  • Pillarbox bars inside panels were ignored. Crop in the edit. Wide storyboard compositions don't survive a later square crop, so generate those finals at 1:1.
  • Transcription timecodes lie. Whisper swallowed a verse's first five lines into repeated "パパパ" and invented 「ご視聴ありがとうございました」 over the outro. Check where the vocal actually starts and ends before timing shots.
  • Asking for varied faces in a crowd failed three times. Make sameness the rule (copies share the protagonist's face), crop the nearest faces out, or put faces in shadow.
  • "Facing camera-left" still flipped. Write profile direction as a visible position.
  • Copies walking beside her read as a girl group, not as being followed. State formation positions relative to her ("she in front, the copies in a V behind her").
  • Unrequested set dressing appears and then must be kept (flower arrangements turned up and changed colour between sheets). Decide once and add it to the World block.
  • "Beat board panel 2" pulled the wrong panel. With a whole sheet attached, the model can't pick a panel by number; it took the panel that matched the prompt text. Crop the panel into its own image before using it as a reference.
  • Research reads text, not video. Section-level timings from research are inference; watch the top references and pull stills before relying on them.

Reference files

  • references/sheet-templates.md: prompt skeletons for beat board and storyboard sheets, the shot-list table format, and the section-jobs table. Read before writing any sheet prompt or table.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.