ShotLock

About

LLMs write storyboards one shot at a time — and every shot looks fine in isolation. Strung together, the holes show up: the heroine's hair changes length at shot 17, the male lead jumps from screen-left to screen-right, a 3-second shot carries 60 characters of dialogue no voice actor can deliver. ShotLock fixes this the same way spec_lock fixes PPT generation: define machine-readable entity tables (characters, scenes) once, have every shot reference them by ID, then let a script verify the references haven't drifted. The model writes content; the script guards consistency. What's inside: - ShotSpec v0.1 — a documented JSON contract for storyboards (meta / characters / scenes / shots), with screen_dir fields that make axis-jump detection possible at all - 15 validation rules in three severities (P0 blocking / P1 serious / P2 advisory): character appearance drift, scene continuity, unregistered references, shot-scale rhythm, establishing-shot presence, axis jumps, speech-rate limits, duration budget, transition legality, emotional monotony, prop hand-flip, subtitle length - Zero-dependency Python engine (3.9+), text and self-contained HTML reports, exit codes that plug into CI - Ships as an Agent Skill (SKILL.md) so Claude Code / Cursor can run the fix loop itself, or as a plain CLI Validated against a deliberately broken sample that triggers all 15 rules, with a clean reference deck and 12 unit tests. MIT licensed.

Tags