HyperFrames Video Beats

Use this skill to turn a talking-head video plus transcript into a paced set of motion graphics that support the narration without covering the speaker unnecessarily.

Core Goal

Keep the viewer oriented and engaged. Every beat must answer one of these:

• What should the viewer remember?
• What concept needs visual structure?
• What stat, contrast, or pivot deserves emphasis?
• Where is the pacing getting quiet enough that the viewer may drift?

Do not add graphics just because a gap exists. Add graphics because the narration has a topic, transition, proof point, or mental model that benefits from visual support.

First Pass

1. Read project instructions (AGENTS.md, local skill docs, and project-specific notes).
2. Inspect the root composition, current beat schedule, shared CSS, and transcript.
3. Build a coverage map from the root data-start / data-duration entries or the master SHOW array.
4. Extract transcript chunks for any requested region and any uncovered gaps.
5. Identify topic spans by narration, not by arbitrary timestamps.
6. Decide whether each topic needs a full-screen paper beat, a lower-third glass card, or no new beat.

Use fast local commands. Prefer rg, Select-String, and small Node/PowerShell transcript scripts.

Beat Type Decision

Use Full-Screen Crumpled Paper

Use a paper takeover when the narration reaches a major thesis, list, section marker, quote, or stat that should briefly become the whole frame.

Good uses:

• Hook payoff or "in this video" overview
• Major section transition
• Big stat or study result
• Memorable thesis line
• Short quote or mantra
• Contrast that needs the audience to stop and look

Rules:

• Keep it short, usually 4-12 seconds.
• Use sparse black text.
• Let only true stat numbers or one extremely important word use accent color.
• Do not cover long explanations with paper takeovers.
• Do not make full-screen text playful, huge, or over-bold by default.