What 418 shared prompts teach about one-shot code video
Skillry collects creators' prompts and remakes each video side by side. The prompts that work share a structure.
Skillry's gallery lists hundreds of videos people made by prompting Claude Opus 5.5, each with the creator's original prompt and a Skillry remake for comparison. Reading through them, a few patterns repeat.
The exploded-view explainer. Prompts from @aichrislee (a heart, a camera lens, a mechanical watch) all follow the same template. Ask for one HTML file with Three.js. List the visible outer parts, then 'the parts you never get to see'. Give one motion rule (the heart beats about once a second). Ask for orbit and zoom, then add an Explode button. The prompts name parts, not adjectives.
The single continuous shot. Strong motion prompts ban cuts outright ('no cuts, no fades') and require each scene to be built out of the previous one. They name one typeface with exact weights and a palette as hex codes.
Sound made in code. Many creators had the agent synthesize the score in Python and sync the effects to cuts. @tetsu_tetsu333 described a full app-tour pipeline: the agent explores the app, writes a spec, takes screenshots, storyboards, generates TTS, splits the narration into phrases so on-screen text appears as each phrase is spoken, and ducks the music under the voice.
Some creators report needing several rounds of pushback. One said the model 'feels a little nerfed' compared with earlier one-shots. Plan for revisions.