templates/STORYBOARD.md
templates/STORYBOARD.mdBrowse 27 files
1,097 tokens
4,578 bytes
Token encoding: o200k_base
Snapshot 24fd22b
← Back to SKILL.md
STORYBOARD —
Film meta
- Product:
- Audience:
- The one feeling:
- Peak scene:
- Assets available up front:
- Sourced-asset findings:
- Assumptions made:
- References taken:
- Moodboard read:
- Style gate verdict:
Arc
| # | Scene | Beat | Intensity (1–10) | layout family | motion family |
|---|---|---|---|---|---|
| 1 | hook | ||||
| 2 | |||||
| … |
Scene 1 — | beat: hook | intensity: N
- purpose: feel: … / learn: …
- subject:
- layout_family / motion_family:
- camera:
- lighting:
- motion:
- transition_in / out:
- scroll_len:
- copy: H: "…" / sub: "…"
- media:
- type:
- route:
- frame prompt:
- motion prompt:
- score:
- fallback:
Gate 0 checklist
- exactly one scene with intensity ≥8
- no two adjacent scenes share layout family or motion family (check the Arc table)
- ≤3 distinct motion families across the whole page
- every scene has real copy and a fallback
- every
media:block is filled: type, route, and — for a GENERATED scene — a literal frame prompt; for a SOURCED or live-3D scene, the equivalent direction to the renderer (subject + camera + lighting + palette), which is what you tune the light rig against; for a type-led scene,none. A one-line "generate something" is not a producible ask - storyboard approved (user) / self-reviewed against the one feeling (autonomous)