Review loop

Loop

1. npm run draft

   — half-resolution render to

   out/draft.mp4

   (fast).

2. npm run sheet

   — one frame per timeline beat, 0.3 s after it so motion has settled, tiled 4×2 into

   out/sheets/beats-N.png

   . Each tile is labelled with its timestamp.
3. Open every sheet image and go through the checklist below.
4. Zoom in on anything suspicious:

   • npm run sheet -- --from 3 --to 5 --every 0.2

     to scrub a transition,

   • npm run sheet -- 3.7 3.75 3.8

     for exact moments,

   • npm run still -- out/still.png --frame=222

     for one full-resolution frame.
5. Fix, then go back to step 1. Stop when a full pass finds nothing.
6. Final:

   npm run build

   , then

   npm run sheet -- --video out/effort.mp4

   and

   npm run wave

   .

Checklist

• One focal point per frame. If two things compete, one of them waits.
• Nothing collides or overlaps unintentionally, especially during transitions where an exiting and an entering element share space.
• Safe area: nothing important within ~60 px of an edge.
• Frame 0 is a real image, not black (it's the X thumbnail).

• Nothing clipped by a mask, container or the frame when it shouldn't be.
• Key message readable when the sheet tile is shrunk to phone width.
• Text isn't moving while it's meant to be read.

• Each readable state holds long enough (see

  motion-design

  §4). If a tile mid-hold shows text still animating, the hold is too short.
• Scenes overlap instead of cutting to empty frames.
• Exits are faster than entrances.

• Only palette colors from

  C

  ; the accent marks the point of the frame.
• Same element looks the same in every scene it appears in.

npm run wave

• Transients sit on beat lines in

  out/wave.png

  .
• −14 LUFS ±1, true peak ≤ −1 dBFS.

Report