Making a scroll-stopping trailer for your AI-made game

When to use it

Use it before you post a game (often one built with an AI coding model) on X, Shorts, TikTok, Reels, Steam, itch.io or OpenDrama. Use it again when earlier posts got views but no clicks, or replies asking whether the footage was real.

Pick the format first:

• Trailer: 20–45 s, 10–15 cuts, led by the music. It sells the mood and the best moment.
• Gameplay demo: 20–60 s, one to three long takes, game audio, a caption like "real-time capture, no cuts". It proves the game is real, and developer audiences on X often prefer it. Many authors post the trailer and put the demo in the first reply.

What the routine fixes, most common first:

1. A slow start. Feeds autoplay muted and people decide in about two seconds. Frame 1 must already move and carry a readable claim. No logo, no fade from black.
2. Dirty capture. Dropped frames, a variable frame rate, a cursor, an FPS counter or browser tabs make a finished game look like a prototype.
3. No structure. A random montage has no peak. You need a hook, the core loop, an escalation, one wow moment and a title card with a link.
4. The wrong aspect ratio. 16:9 in a 9:16 feed becomes a thin strip, and a blind centre crop loses the action.

Not covered here: making the game itself look better (console-grade look in Three.js) and the names of camera moves (camera language). If you only need the plan, the trailer shot-list prompt writes it.