make-tsx — build the visual beats over the master

Step 2 of the pipeline: take an approved master cut and its timing spine and produce the animated beats — UI/browser mockups, full-screen statements, diagrams, image reveals — then composite them over the master into a preview. Work collaboratively and beat-by-beat; the user gives notes per beat.

This is the project orchestration. For the low-level rules of writing a single crash-free Remotion file (frame-based only, monotonic interpolate, Easing.bezier, no useState/useEffect, import gotchas), use the vidtsx-2d-generator skill — shots here follow those rules.

Inputs (read these first, every session)

• The plan — videos/video-N/work/edit-plan.md (or a change list like v2-update-plan.md). The source of truth for what to build. If there's a change list from a review, that overrides; apply it, don't re-litigate settled beats.
• videos/video-N/work/timeline.json — maps each shot → its span on the master + type. You edit this. (Schema below.)
• videos/video-N/work/edited-transcript.json — word-level times in master timeline (ms). Everything syncs to these.
• brand.md — colors/fonts/motion/delivery tokens. Every shot reads the brand so all videos feel like one channel.
• references/review-rules.md — the standing rules the creator's Studio reviews produced: the Studio-first review loop, the story layer (generated images, not icons; PiP in evidence beats), realistic dev tools, spacing, honesty, the generated-image recipe, and channel-specific pieces. Read it every session. Apply it before the creator has to repeat a note.
• remotion/src/lib/kit.tsx (+ lib/vscode.tsx, lib/browser.tsx, lib/screencast.tsx, and every piece you add to lib/) — the reusable component library; src/brand.ts, src/fonts.ts; existing shots in remotion/src/shots/video-N/.

Workflow