Frame Break X03

Pairs well with

# CES style instruction — X03 Frame Break

You are an experienced motion designer and video editor working in Claude Code. Apply the **X03 Frame Break** 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

**Signature Effects** — The footage first plays inside a device or picture frame, then a foreground element pushes past the frame edge: the part beyond the boundary is drawn in front of the bezel while the rest stays inside the screen. The broken boundary creates a playful 3D pop that stops the scroll. True frame break on live footage needs a subject matte; without one, the same pop is done with a supplied transparent cutout such as a product, sticker or still of the subject.

### X03 Frame Break

- **When:** ≈ 00:00.00 → 00:03.00 (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** V1 (main picture)
- **What it does:** The speaker or a supplied cutout bursts out of a stylised phone frame — rising past the bezel so part of them sits in front of the frame.
- **Parameters:** Render mode: Auto (use mask if available, else 2D); Frame type: Phone frame; Break edge: Top edge; Break distance: 35%; Frame tilt: 8 deg; Overlap shadow: on; Easing: Back out (overshoot)
- **Steps:**
  1. PREREQUISITE CHECK: having the speaker extend past the frame edge requires their matte so the outside portion can be drawn over the bezel, which needs a clean subject matte (supplied, or from an external segmentation step checked for edge flicker). If a usable matte exists, build the full version; otherwise use the 2D version — use a supplied transparent cutout (product PNG, sticker, logo or a still of the subject already cut out) as the breaking element; the live footage stays entirely inside the screen and the cutout bursts out of its top edge. Tell the user which version was rendered.
  2. Composite a stylised, unbranded phone (≈ 62% of frame width, thick dark bezel, 12% corner radius) over a dark, blurred copy of the footage, tilted 8° (rotateX 5°, rotate −3°) with CSS perspective ≈ 2160px. The source footage plays inside the screen area.
  3. Split the breaking element into two copies sharing one transform: copy A clipped to the screen rectangle (behind the bezel), copy B (matte-cut or cutout) clipped to everything beyond the top screen edge and layered above the bezel. Together they read as one element leaving the screen.
  4. Animation: over 17 frames the element rises until 35% of its height is past the top edge, using a back-out curve with slight overshoot (cubic-bezier(0.34, 1.56, 0.64, 1)); hold, then settle back 11% at the end of the range.
  5. Cast a soft shadow from copy B onto the bezel/frame (offset 1% of frame width, blur 2.5%, 40% opacity) — this shadow is what sells the depth.
  6. Verify the boundary on every frame: no halo or missing hair where copies A and B meet, and the face is fully readable. Use only the supplied media — never generate, mock up or invent cards, screens, numbers or claims.
- **Assets:** Source video (⚠ MISSING) · optional: Subject mask / matte, Product image, Photos
- **Fallback:** Without a subject matte, break the frame with a supplied transparent cutout (product, logo, sticker or a still cutout photo of the subject) instead of the live footage. If no cutout asset exists either, use L04 Floating Device Frame with a punch-in rather than faking the break.

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