make-a-trailerlisted

# make-a-trailer Point this at any project and it ships a cinematic vertical trailer for social — you approve **twice** (a static animatic, then the motion cut), everything else runs hands-free. ## Ground rule **One character, one world, two gates.** A trailer reads as *professional* when the face, style, and world stay identical across every scene and the whole cut lands one feeling — not when each frame is individually pretty. So: **lock a style + character bible before generating anything**, drive every image and clip from it, and record every job in a **resumable manifest** so a dead render resumes instead of re-spending credits. Claude directs; ChatGPT writes + draws; Higgsfield/Flow/Seedance move; ffmpeg cuts. Never claim a step ran that didn't — the manifest is the truth. **Static-first — see the whole trailer before you buy a single motion clip.** Motion is the one expensive, slow step. So assemble every keyframe into a held-still **animatic** (each beat ≈1s, blurred-fill so no wide action is cropped, under a scratch music bed), watch it end-to-end, and lock order + pacing + continuity *there*. Only approved scenes ever get animated — this is what makes it cleaner (bad beats die on cheap stills) and faster (no re-rendering motion you cut). **Two browsers beat one.** Generate the keyframes across two ChatGPT accounts in parallel — Chrome on one CDP port, Brave on another — one bible-anchored conversation per browser, the scene list split zigzag between them. ~2× t