Magnifito Storyboard & Scene Planner
The magnifito-storyboard skill structures the narrative arc of the video, mapping client objectives and factual claims to concrete visual scenes and timing.
Contract Specification: scene-plan.json
Every storyboard translates into scene-plan.json conforming to ScenePlanSchema:
plan_revision: String identifier (e.g. rev-1).
renderer: Target renderer (hyperframes, html, remotion, motion).
timing_authority: Clock master (speech, music, template, manual).
scenes: Array of scene objects:
scene_id: Unique identifier (e.g., scene-01-hook).
factual_purpose: High-level explanation of the scene's communication goal.
duration_seconds & duration_frames: Explicit timing.
copy_text: The exact text to appear on screen or be spoken.
claims_refs: Array of claim_id strings linking this scene to claims.json.
asset_refs: Array of asset_id strings from assets.json.
visual_recipe: Chosen style recipe (e.g., kinetic-typography, product-reveal, retail-card). With renderer: "motion" only the motion-* recipes are valid (see below).
audio_events: Keyframe-timed cues for voiceover, sound effects, or music.
Planning for the Motion Engine
When renderer is motion, every scene uses one of the recipes in styles/recipes/motion-*.json (their engines field is ["motion"]), and copy_text follows the recipe's convention, with | separating segments:
motion-kinetic-type (2.5–6 s): one phrase, up to 24 words.
motion-card-morph (3.4–7 s): Headline | row | row | …, up to 4 rows.
motion-bars-chart (2.8–6 s): Title | Label: value | …, every value backed by a claims_refs entry.
motion-logo-reveal (1.8–5 s): the tagline, with the logo in asset_refs. Put it last.
Each clip opens from and closes on the same centred dot, so plan scenes back to back without transition scenes. See fixtures/motion-demo/scene-plan.json.
Narrative Discipline
- The 15-Second Launch Promo Formula:
0.0s - 4.0s: Hook & Context (state audience problem or question).
4.0s - 10.0s: Core Factual Advantage (reveal product feature, linked to claim-1).
10.0s - 15.0s: Call to Action & Proof (link to claim-2, trial action URL).
- Claims Linkage:
- Every metric, discount, accreditation, or timeline in
copy_text must explicitly cite a claim_id.
- Modifying copy invalidates the scene plan and requires re-running validation.
References: reference/motion-timing.md (durations, stagger, reading holds, scene order) and reference/script-and-shot-plan.md (evidence-linked script and shot plan onto claims, brief and scene plan).
Stopping Conditions
- Fail immediately if any
claims_refs identifier is not found in claims.json.
- Fail if sum of scene durations does not equal
brief.duration_seconds.
1---2name: magnifito-storyboard3description: "Convert client brief and claims register into a timed, claims-linked scene plan with visual recipes."4metadata:5 source: https://skillmd.com/skills/magnifito/magnifito-storyboard6---78# Magnifito Storyboard & Scene Planner910The `magnifito-storyboard` skill structures the narrative arc of the video, mapping client objectives and factual claims to concrete visual scenes and timing.1112## Contract Specification: `scene-plan.json`1314Every storyboard translates into `scene-plan.json` conforming to `ScenePlanSchema`:1516- `plan_revision`: String identifier (e.g. `rev-1`).17- `renderer`: Target renderer (`hyperframes`, `html`, `remotion`, `motion`).18- `timing_authority`: Clock master (`speech`, `music`, `template`, `manual`).19- `scenes`: Array of scene objects:20 - `scene_id`: Unique identifier (e.g., `scene-01-hook`).21 - `factual_purpose`: High-level explanation of the scene's communication goal.22 - `duration_seconds` & `duration_frames`: Explicit timing.23 - `copy_text`: The exact text to appear on screen or be spoken.24 - `claims_refs`: Array of `claim_id` strings linking this scene to `claims.json`.25 - `asset_refs`: Array of `asset_id` strings from `assets.json`.26 - `visual_recipe`: Chosen style recipe (e.g., `kinetic-typography`, `product-reveal`, `retail-card`). With `renderer: "motion"` only the `motion-*` recipes are valid (see below).27 - `audio_events`: Keyframe-timed cues for voiceover, sound effects, or music.2829## Planning for the Motion Engine3031When `renderer` is `motion`, every scene uses one of the recipes in `styles/recipes/motion-*.json` (their `engines` field is `["motion"]`), and `copy_text` follows the recipe's convention, with `|` separating segments:3233- `motion-kinetic-type` (2.5–6 s): one phrase, up to 24 words.34- `motion-card-morph` (3.4–7 s): `Headline | row | row | …`, up to 4 rows.35- `motion-bars-chart` (2.8–6 s): `Title | Label: value | …`, every value backed by a `claims_refs` entry.36- `motion-logo-reveal` (1.8–5 s): the tagline, with the logo in `asset_refs`. Put it last.3738Each clip opens from and closes on the same centred dot, so plan scenes back to back without transition scenes. See `fixtures/motion-demo/scene-plan.json`.3940## Narrative Discipline41421. **The 15-Second Launch Promo Formula**:43 - `0.0s - 4.0s`: Hook & Context (state audience problem or question).44 - `4.0s - 10.0s`: Core Factual Advantage (reveal product feature, linked to `claim-1`).45 - `10.0s - 15.0s`: Call to Action & Proof (link to `claim-2`, trial action URL).462. **Claims Linkage**:47 - Every metric, discount, accreditation, or timeline in `copy_text` must explicitly cite a `claim_id`.48 - Modifying copy invalidates the scene plan and requires re-running validation.4950References: `reference/motion-timing.md` (durations, stagger, reading holds, scene order) and `reference/script-and-shot-plan.md` (evidence-linked script and shot plan onto claims, brief and scene plan).5152## Stopping Conditions5354- Fail immediately if any `claims_refs` identifier is not found in `claims.json`.55- Fail if sum of scene durations does not equal `brief.duration_seconds`.56