venice-video-harness: Command for Claude Code

Workshop an episode script collaboratively with the user.

Direct before you draft. If the idea is vague, run the Seedance 2.0 Skill OS seedance-interview (short form for a fast brief); for a longer or multi-clip story run seedance-sequence to set the story spine and one directorial voice. Then, for every shot, name one intention and derive camera/light/blocking/performance/sound from it — do NOT stack "cinematic" adjectives. Read each drafted description back through directing-engine, and strip empty quality-boosters with seedance-antislop + vocab/*. If Seedance OS isn't installed, apply the same principle from memory (see this repo's README "Directing layer"). The in-code workshop system prompt (src/mini-drama/cli.ts) already carries this instruction; a directed concept from the user is what makes it land.

Author the geometry, not just the action (rule 49). Spatial consistency is built into the script, not patched at generation time. Give every location a spatialAnchors field (3-5 named landmarks and their fixed relative positions) and every character shot a blocking field: each character/object's position relative to those named anchors, their frame side (screen left/center/right), depth (foreground/background), and facing/eyeline. Across consecutive shots in a scene, characters keep their screen sides and relative positions unless a movement is written into the action; preserve screen direction and eyelines (180-degree rule); close-ups still name what's behind/beside the subject.

1. Ask the user for the episode concept/outline (what happens in this episode?)
2. Draft a shot-by-shot script in the EpisodeScript JSON format
3. Each shot should specify:
   • type (establishing/dialogue/action/reaction/insert/close-up)
   • duration (3s/5s/8s/10s/13s/15s)
   • videoModel ("action" for movement/dialogue, "atmosphere" for establishing/static)
   • description (visual scene description)
   • location (slug of a defined location)
   • blocking (concrete geometry: positions vs named location anchors, frame side, depth, facing/eyeline — consistent with adjacent shots)
   • characters present
   • dialogue (if any)
   • sfx (optional sound effects hint)
   • cameraMovement
   • transition -- affects video generation frame handling:
     • CUT (default): sharp edit, each shot starts from its own panel, ends naturally
     • FADE: gentle transition, chains start frame from previous video
     • DISSOLVE: smooth blend, chains start frame AND targets next panel as end frame
     • MATCH CUT: compositional match, chains start + targets end frame
     • SMASH CUT: abrupt jarring cut, no linking at all Use CUT for most shots. Only use DISSOLVE/MATCH CUT when you specifically want the video to morph toward the next panel's composition.
   • dialogue delivery (tone/manner for voice generation, e.g. "in a cold manner", "nervously", "whispering seductively")
4. Total duration should target ~60 seconds
5. Present the script to the user for review/edits
6. Once approved, save to the episode directory:

npx tsx src/mini-drama/cli.ts new-series  # (if needed to ensure episode dir exists)

Then write the script.json to: output//episodes/episode-NNN/script.json

The script format:

{
  "episode": 1,
  "title": "The Betrayal",
  "seriesName": "series-name",
  "totalDuration": "60s",
  "shots": [...]
}