Screen tutorial
Read references/house-rules.md first; it wins. Run order: video-director section 3. This file only covers what is specific.
Status: rebuilt look-alike screens are proven (the Search Console + Cloudflare video); screenshots in the screen beat are proven. Playing a real screen recording inside the zooming window is not built yet: build and test it on the first real recording (extend the screen beat to take video, as the clip beat does), then update this line.
What's specific
- Where the screens come from (hard rule 2): the user's own screen recording if they have one; otherwise rebuild the steps as HTML look-alikes from current, dated references (
references/screens.md), with cursor, clicks, typing and focus. That's a demonstration, so rebuilding is right. Existing modules to reuse:gsc-add-property,cloudflare-dns-add,gsc-verify. - What must still be real: any claim about the product ("Google says…") is a receipt captured from its docs, and any static page shown as itself (a homepage, a pricing page) is a capture.
- Check for private data in every frame used (emails, account ids, keys, revenue). Blur or crop it and tell the user.
- Source:
fetch-video.sh→enhance-audio.sh→rough-cut.mjs(it cuts picture and sound together, so dead time and retakes go) →voice.mjs --provider file. - Each step is a
screenbeat with the recording (or screenshot) in the brand window and cameramoves: start wide, push to the control as it's named (1.3–1.6×), hold, pull back. Never a laptop or device frame. - Step marker top-right from
script.json→steps. A stamp or highlight on the thing to click. One instruction per beat, named the way the screen labels it. - Structure: hook (the problem, 5–10 s; on camera if they filmed themselves) → the whole job in one line → the steps → the result → one extra tip.
- Kit use is light: receipts for claims about the product (its own docs), a reaction or meme sound on the "it worked" or "it failed" moments. No cutaway mid-step.
- Rebuilt screens use placeholder data (
example.com), never a real account's details. - Pacing: calm. The viewer is following along.
Cost and time
Transcription only (cents). Render ≈ 1–1.5 min per minute of video.
References
own-footage.md · engine-api.md (screen beat, camera moves) · screens.md (rebuilding app screens for demonstrations) · voice-music.md · troubleshooting.md