11 production pipelines, 47 tools, 124 agent skills. Supports cloud APIs (fal.ai, OpenAI, ElevenLabs, Suno, HeyGen, Runway) and free local providers (diffusers, Piper TTS, WAN 2.1, Hunyuan, CogVideo). Co-authored-by: Hanzo Dev <[email protected]>
4.3 KiB
Scene Director - Screen Demo Pipeline
When To Use
You are planning how the viewer's attention moves through an existing screen capture. The source video already exists; your job is to decide when to stay wide, when to crop in, and when to add minimal guidance.
Prerequisites
| Layer | Resource | Purpose |
|---|---|---|
| Schema | schemas/artifacts/scene_plan.schema.json |
Artifact validation |
| Prior artifacts | state.artifacts["script"]["script"], state.artifacts["idea"]["brief"] |
Script timing and source notes |
| Tools | frame_sampler, scene_detect |
Extract reference frames and transitions |
| Playbook | Active style playbook | Overlay style and pacing rules |
Process
1. Plan Attention, Not Constant Motion
Modern screen-demo tools converge on click-led zoom because it reduces random camera motion. Use that principle here:
- zoom when the viewer truly needs help reading or locating something,
- stay steady during comprehension,
- zoom manually when the key event has no click anchor,
- reset to a wider context between major steps.
Use frame_sampler for exact reference frames around each key action and store detailed crop notes in scene_plan.metadata.
2. Choose Scene Shapes
Use simple scene types that match the schema:
screen_recordingfor live UI capture sectionstext_cardfor step labels, title cards, or recap slidesdiagramonly when the UI alone cannot explain the concepttransitionsparingly between major workflow phases
3. Plan Crop Strategy In Metadata
The schema does not have first-class zoom objects, so keep the scene descriptions concise and place the detailed crop plan in scene_plan.metadata.crop_regions.
Recommended crop_regions fields:
section_idstart_secondsend_secondsregionzoom_leveltrigger(click_cluster,typing,result,manual_focus)transition_durationrationale
Useful heuristics:
| UI Element | Zoom Level | Region Sizing | Notes |
|---|---|---|---|
| Terminal / code | 1.5-2.2x | keep enough surrounding context to orient the viewer | |
| Small button / icon | 2.0-3.0x | show padding so the viewer knows where it lives | |
| Modal / dialog | 1.4-2.0x | capture the full modal, not a partial crop | |
| Full-page result | 1.0-1.3x | show more context before zooming again |
4. Plan Callouts With Restraint
Document overlay needs in required_assets and metadata.callout_plan.
Use only the patterns that clarify the action:
highlight_boxarrowstep_labelkeystroke_badgeblur_mask
Rules:
- no more than two attention cues at once,
- show the cue just before the action,
- remove it quickly after the action,
- prefer highlight or zoom; do not stack both unless readability truly demands it.
5. Plan Speed Treatment
Mark repetitive segments as either:
speed_upcutrealtime
Useful visual treatments for sped-up sections:
- progress label,
- small status text,
- simple dissolve over the removed wait.
Do not invent flashy transition behavior for installs, builds, or long typing stretches.
6. Choose Aspect Ratio Per Segment
If the whole project targets multiple outputs, note in metadata which scene crops are viable for:
16:91:19:16
If a step cannot survive vertical, say so. The correct answer is sometimes to ship landscape only or create a separate simplified vertical cut.
7. Quality Gate
Zoom coherence:
- motion is intentional, not constant
- every zoom exists for legibility or orientation
- every major section gets a wider re-establishing view
- crops do not cut off the relevant text or control
Callout coherence:
- every critical action has either a crop or a callout
- callouts do not obscure the UI
- subtitle and callout zones do not collide
- sensitive data has a planned mask
Pacing coherence:
- result moments stay at normal speed
- waiting and repetitive typing are compressed or removed
- the output duration still matches the brief
Common Pitfalls
- Staying zoomed in so long that the viewer loses the interface map.
- Planning vertical crops for wide UI without admitting they fail.
- Adding highlight layers everywhere instead of choosing the single clearest cue.
- Ignoring sensitive data revealed in seemingly minor frames.