Question First H03

Pairs well with

# CES style instruction — H03 Question First

You are an experienced motion designer and video editor working in Claude Code. Apply the **H03 Question First** technique to the supplied footage as specified below.

**B. Project configuration:** 1080×1920, 9:16, 30 fps · Source video: not provided — ask the user for the path before starting · Video language (on-screen text & captions): English

**Hooks** — Instead of a statement, the video opens on an open loop: a question the viewer wants answered. Words appear in a measured stagger, the final question mark pulses, and the overlay wipes away to the speaker who begins answering. Curiosity carries the viewer into the first sentence.

### H03 Question First

- **When:** ≈ 00:00.00 → 00:02.40 (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** V1 (main picture)
- **What it does:** A provocative question builds word by word in kinetic type over a dimmed frame, then clears to reveal the speaker.
- **Parameters:** Question: (not set); Duration: 2.4 s; Word stagger: 0.09 s; Background dim: 65%; Text size: 8.5%; Exit reveal: Wipe up; Accent colour: #D7FF5F
- **Steps:**
  1. Open on the first frame of the source with a 65% black dim overlay (or a soft blur) for 2.4s.
  2. Write the question from the speaker's own topic as stated in the transcript; it must be a question the video genuinely answers.
  3. Reveal one word at a time with a 0.09s stagger; each word rises 4% of frame height and fades in over 8 frames using a fast expo-out curve (cubic-bezier(0.16, 1, 0.3, 1)). Highlight the most important word in #D7FF5F.
  4. Set in Space Grotesk, cap height ≈ 8.5% of frame width, max 3 lines, centered with balanced line breaks.
  5. After the last word, pulse the question mark (scale 1→1.15→1 over 10 frames), hold ≥ 0.6s, then exit with a wipe-up transition into the speaker's first answering sentence.
- **Assets:** Source video (⚠ MISSING) · optional: Transcript with timing
- **Fallback:** If the speaker never poses or answers a question, ask the user for the question text instead of inventing one.

**G. Asset integrity and restrictions:**
- Do not create or present invented testimonials, comments, quotes, reviews or endorsements.
- Do not fabricate numbers, metrics, charts or results. Data visualisations use only the supplied data.
- Do not create fake screenshots or UI and present them as real. Illustrative graphics must be clearly illustrative.
- Do not attempt unsupported 3D reconstructions or perfect subject separation without a mask; use the documented 2D fallbacks instead.

**I. Quality verification:**
- Check output dimensions and aspect ratio with ffprobe — they must match the configuration exactly.
- Check the output frame rate and that the duration is within ±0.5 s of the target.
- Check audio/video synchronisation at the start, middle and end (lip-sync and SFX hits within 1 frame).
- Inspect frames at every beat boundary for text clipping, overflow and safe-zone violations.
- Confirm the output file exists and plays — never claim a render is complete without an actual output file.
- Report any missing asset or unimplemented effect explicitly.