agentleFS
LordVayronLordVayron/video-factory/.claude/skills/cinematographer/SKILL.md

cinematographer

Skill67 starsChanged 18 days agoMITView on GitHub

Turns an approved script into scenes, blocking sheets and shots (projects/<slug>/shotlist.json) built for continuity — each scene is storyboarded as one grid image and filmed as one multi-shot generation, so characters keep their positions, props and screen sides across cuts. Use after the script is approved, when shots break continuity, or when planning coverage for dialogue.

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. QinghongLin/data2story-skill★ 155same 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 repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read references/cinematography.md (film grammar, look) and references/models.md (models) once per session.

    line 8
  2. Distinctive:

    Cut on action or on the punchline word;: keep the reaction beat (0.5–1 s) after the line.

    line 38
  3. Distinctive:

    Every scene ≤ 15 s with 2–5 shots.

    line 42
  4. Distinctive:

    Every shot has framing, lens, camera, image, motion, dialogue (or none) and sfx.

    line 43
  5. Very specific:

    If the story needs a character somewhere else, add a shot whose moves says where to and how, and whose action shows the movement: "moves": …

    line 49
  6. Distinctive:

    Singles are dirty singles: When characters share furniture, a close-up keeps the partner's edge (fur, ear, shoulder) at their screen side.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Cinematographer

Read references/cinematography.md (film grammar, look) and references/models.md (models) once per session.

Think in scenes, not shots

Research (Higgsfield Popcorn, Wan 3.0 / Seedance 2.0 multi-shot): AI models keep continuity when a scene is generated together, and lose it when each shot is generated alone. So:

  • Scene = one location, one continuous moment, ≤ 15 s, 2–5 shots of 2–5 s each.
  • Storyboard = ONE grid image per scene (all panels in one generation) → split into panels.
  • Video = ONE multi-shot generation per scene (Shot 1 [0-3s] … Hard cut. Shot 2 [3-6s] …), opening on the scene's first panel, with character and set references and voice references.
  • A 20 s episode is typically 2 scenes → 2 grid images + 2 video generations, all run in parallel.

shotlist.json

"scenes": [
  { "id": "A", "summary": "one line: what happens", "shots": ["s01","s02","s03"],
    "blocking": "Milo sits on the LEFT chair at the round table facing right, paper in front of him; Rex sits on the RIGHT chair facing left; Ana is not in the room." }
],
"shots": [ { "id": "s01", "duration": 3, "characters": ["milo","rex"], "framing": "medium two-shot", "lens": "35mm lens", "camera": "fixed camera",
             "image": "frozen moment for the storyboard panel", "motion": "what changes in this shot",
             "dialogue": [{ "char": "milo", "text": "…", "delivery": "…" }], "sfx": "…" } ]

Blocking sheet (write it before the shots)

For every scene: each character's position (which chair, left/right of frame), facing, posture, props in hand, and any movement with its timing ("in s03 Rex stands up and moves to the doorway"). If a character moves, the next shot starts where they ended. The blocking text goes into the storyboard grid prompt and the video prompt verbatim.

Coverage that keeps continuity

  • Anchor with the two-shot. Dialogue between two seated characters plays mostly in a medium two-shot; cut in for reactions and punchlines.
  • Singles show the geography: a close shot of one character keeps the table and the other's shoulder or edge in frame (over-the-shoulder), against the same background wall every time.
  • 180° rule: screen sides never flip. Write "Milo frame left, Rex frame right" in every shot that has both.
  • Name the camera in every shot ("fixed camera", "slow push-in"). Unnamed cameras make Wan cut on its own.
  • Moves come from the catalog: set shot.move to one of engine/lib/camera.mjs MOVES (static, push-in, pull-out, truck, pan, tilt, orbit, crane, handheld, follow, rack-focus, overhead; bold: crash-zoom, dolly-zoom, whip-pan, fpv-drone). One move per shot, at most one bold move per film. The project's camera kit sets the optics; a shot can change it with shot.rig ({ "kit": "vintage-16" } for a flashback, { "focal": 85 } for a close-up). Close-ups of faces at 50-85mm, never under 24mm unless the creator asks.
  • Physical comedy in the wide, so the whole action reads.
  • Cut on action or on the punchline word; keep the reaction beat (0.5–1 s) after the line.
  • No impossible jumps: a character can't be at the table in s02 and in the middle of the room in s03 unless a shot shows them moving.

Before handing off

  • Every scene ≤ 15 s with 2–5 shots; the total matches the script runtime.
  • Every shot has framing, lens, camera, image, motion, dialogue (or none) and sfx.
  • node engine/gen.mjs estimate <slug>.

Continuity logic (hard rules, enforced by engine/continuity.mjs)

  • Every scene declares seats. Each character gets a place and a screen side: { "rex": { "place": "the RIGHT cushion of the couch", "side": "right" } }. Prompts repeat it as a SEAT LOCK in every shot, wides included.
  • Nobody changes place off screen.
    • If the story needs a character somewhere else, add a shot whose moves says where to and how, and whose action shows the movement: "moves": { "rex": { "to": "the rug", "side": "right", "how": "hops down off the couch" } }.
    • The plan check fails if a later scene starts a character somewhere new without that shot.
  • Singles are dirty singles. When characters share furniture, a close-up keeps the partner's edge (fur, ear, shoulder) at their screen side. The seat beside the subject is never empty.
  • After filming, run node engine/continuity.mjs <slug>.
    • A vision judge reads one frame per shot and compares it with the plan: furniture/floor, side, teleports, night or day, empty partner seat, room, wardrobe.
    • A failing take can't be cut (edit.mjs refuses it). Reroll it with a note naming the violation.

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.