Self-review loop: have Opus score its own frames, redo only the worst 3 clips
FinanceYF5 · x · 2026-11-10
Step 11 of the tutorial series covers the self-review loop: export beat contact sheets, fast-action frame strips, a 360px mobile preview and loop checks so Opus can actually "see" its own output.
Score the piece on hook (first 2s), readability, motion, composition, brand accuracy and A/V sync, identify the worst 3 time segments, and redo only those until everything scores 8+. Quoted case: a 45-second hand-painted animated short made with Opus 5.5 in pure code — 62.7M tokens (96% cache reads), 163 model calls, $34 at list price, 6¾ hrs total with only 1½ hrs hands-on.
More from coding & agent
- Math explainer video on extreme value theorem built in 40 minutes with Codex — cloneofsimo · 2026-11-10
- Use mind-shaped priors when working with LLMs, argues researcher — Sauers_ · 2026-11-10
- Busy: open-source AI agent hub you deploy on your own Vercel account — evilrabbit_ · 2026-11-10
- Preprint: Learning Tool-Output Projections from Agent Traces Cuts Billed Tokens up to 56% — solyarisoftware · 2026-11-10
- Dev says he hasn't manually written code in 2 years, dating back to Alex Sidebar work — rudrank · 2026-11-10
- Fable 5.2 built the same game twice—with and without ElevenLabs MCP, and the audio gap is striking — mhdfaran · 2026-11-10