Choreographs device and app-window reveal shots for launch films - chassis settles from 0.92 to 1.0 scale, screen ignition delayed 100-200ms after the frame lands, a single timed light sweep to sell the material, then a slow camera push - so hardware and product windows arrive with mass instead of popping in like a slide transition. Use when someone asks "how should the phone reveal animate in our trailer", "the device reveal looks like a slide transition", "when should the screen content light up during the reveal", or "animate the app window arriving in the launch video", or whenever a marketing shot introduces a device, browser window, or app frame for the first time. Do NOT use for in-product UI transitions or motion tokens - use animation-system or motion-spec instead; for the cursor and typing inside the screen after ignition, use marketing-ui-animation; for building the shot in code, use remotion-compose.
---
name: device-reveal-choreography
description: Choreographs device and app-window reveal shots for launch films - chassis settles from 0.92 to 1.0 scale, screen ignition delayed 100-200ms after the frame lands, a single timed light sweep to sell the material, then a slow camera push - so hardware and product windows arrive with mass instead of popping in like a slide transition. Use when someone asks "how should the phone reveal animate in our trailer", "the device reveal looks like a slide transition", "when should the screen content light up during the reveal", or "animate the app window arriving in the launch video", or whenever a marketing shot introduces a device, browser window, or app frame for the first time. Do NOT use for in-product UI transitions or motion tokens - use animation-system or motion-spec instead; for the cursor and typing inside the screen after ignition, use marketing-ui-animation; for building the shot in code, use remotion-compose.
---
# device-reveal-choreography
You choreograph arrivals. The PowerPoint reveal - scale-from-zero, a fast spin, screen already glowing - is the single fastest way to make hardware look weightless and software look fake. The fixed order (object, then content, then light, then camera) mirrors how people encounter real devices; skipping a stage is what viewers feel as "cheap" without naming it.
## Operating procedure
Run the stages in order: each stage keys off the previous stage's end frame - ignition cannot be timed until the settle frame exists, and the sweep cannot start until ignition does.
### Step 1: Gather the shot inputs
Paste the charter block if one exists. If the client has a charter but the foundations pack is not installed, elicit the needed values directly and label them provisional. If no charter exists at all, halt and route to premium-design-foundations - never substitute worked-example values. The charter must include the motion fork's damping ratio and bounce policy. Then ask for:
1. **Subject**: hardware, browser window, or app frame.
2. **Screen contents**: the real product UI carrying the campaign fixture dataset defined in marketing-screenshot-craft, cited never re-created. Refuse placeholders. If that pack is not installed, elicit the client's fixture records directly and label them provisional.
3. **Shot length** in frames, and the fps.
4. **Grid**: whether the shot sits on a trailer grid. If yes, pull beat and downbeat frames from launch-trailer-director; if that skill is not installed, ask for BPM and fps directly, derive the beat, and label the grid provisional.
If any input is a guess, label it a guess and move on.
### Step 2: Stage the chassis settle