Explainer Icon Flow B04

Pairs well with

# CES style instruction — B04 Explainer Icon Flow

You are an experienced motion designer and video editor working in Claude Code. Apply the **B04 Explainer Icon Flow** 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

**Animated B-Roll** — A short process or relationship is drawn as simple icon nodes joined by lines. Each node lands on the word where the speaker names that step, and the connector to the next one draws out like a pen stroke, so the structure builds at the pace of speech. Clear iconography makes an abstract sequence concrete without needing footage of it.

### B04 Explainer Icon Flow

- **When:** ≈ 00:00.00 → 00:05.00 (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** V1 (main picture)
- **What it does:** An icon for each step pops in one by one and animated connectors draw between them, mapping the process the speaker describes as they say it.
- **Parameters:** Step labels: (not set); Flow layout: Vertical chain; Connector style: Line with travelling pulse; Delay between steps: 0.6 s; Icon style: Outline icons; Accent colour: #D7FF5F; Easing: Back out (overshoot)
- **Steps:**
  1. Cut to an icon-flow cutaway from 00:00.00 to 00:05.00. Take the steps (3–5) and their order strictly from what the speaker says in the transcript during this range; if the speaker does not describe a clear sequence, ask the user for the steps instead of inventing one.
  2. Pick one literal icon per step from an openly licensed set (e.g. Lucide, ISC licence) — a #D7FF5F outline glyph (stroke ≈ 0.5% of frame width) in a dark rounded tile, ≈ 14% of frame width. No brand logos unless the user supplied them.
  3. Arrange the nodes as a vertical chain centred in the frame, nodes evenly spaced between 18% and 78% of frame height; labels sit beside or under each node in Inter semibold at ≈ 4.5% of frame width.
  4. Timing: node i lands at range start + i × 0.60s (≈ 18 frames apart) — or, better, on the frame where the speaker says that step. Each node scales 0 → 1 over 9 frames with a back-out curve with slight overshoot (cubic-bezier(0.34, 1.56, 0.64, 1)); its label fades up 4 frames later.
  5. Connectors: SVG paths with pathLength=1, drawn by animating stroke-dashoffset 1 → 0 over 13 frames just before the next node lands. After each connector is drawn, send a small #D7FF5F pulse dot along it once to show direction.
  6. Hold the completed flow ≥ 1s before cutting back, and keep everything inside an 8% safe margin.
- **Assets:** Transcript with timing (⚠ MISSING) · optional: Brand fonts
- **Fallback:** If no transcript is available, ask for the step labels. If no suitable licensed icon exists for a step, use a numbered badge instead of an unrelated pictogram.

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