Contrarian Hook H09

Pairs well with

# CES style instruction — H09 Contrarian Hook

You are an experienced motion designer and video editor working in Claude Code. Apply the **H09 Contrarian Hook** 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** — The conventional wisdom appears first, then gets visibly challenged: a strike-through, a swap or a physical collision pushes it aside for the speaker's counter-position. It frames the video as a debate the viewer wants to see resolved.

### H09 Contrarian Hook

- **When:** ≈ 00:00.00 → 00:02.60 (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** V1 (main picture)
- **What it does:** Two opposing statements collide on screen — the common belief is struck out and the counter-claim takes its place.
- **Parameters:** Common belief: (not set); Counter-claim: (not set); Collision style: Strike-through and replace; Duration: 2.6 s; Belief colour: #FF7A6B; Accent colour: #D7FF5F
- **Steps:**
  1. Derive Statement A (the belief the speaker argues against) and Statement B (the speaker's position) strictly from the transcript; both must be things the speaker actually says.
  2. Show A first in Space Grotesk with #FF7A6B tint, centered in the upper third, for ~40% of the 2.6s duration.
  3. Draw a strike-through line across A over 6 frames, drop A's opacity to 40%, then reveal B beneath it with a 10-frame rise.
  4. Render B in #D7FF5F or white with the accent underline; hold until the speaker begins explaining.
- **Assets:** Source video (⚠ MISSING) · optional: Transcript with timing
- **Fallback:** If the speaker does not explicitly state an opposing belief, ask the user for both statements rather than inventing a strawman.

**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.