A CLAUDE.md checklist for frame-by-frame video rendered in code with Opus 5.5
The author notes that Opus 5.5 cannot output video directly and that viral short films are actually frames rendered by code, then gives three render self-check rules and a one-line fix for a frozen shot.
unsealed: opus 5.5 can't output video. every viral reel in this wave is code that draws the frames CLAUDE.md the agent rereads this file before every run. it already knows taste. what it's missing is three checks: > two renders of the same range give the same hash. if they don't, the model remembered something between frames > the picture never sits still longer than a second and a half > the jump at the loop is no bigger than a normal step between frames counted: 15 seconds at 60 fps is 900 calls to seek(t) and zero timers frozen shot 2.15 s → 1.33 s after a one line fix every frame depends only on time. so a fix is one line, not a rebuild ↓ which check would you add as the fourth?
This post quotes another post: x.com/vorty279/status/2107883030475903259