Open source
Reusable production systems
A short prompt is cheap when a style library and two human approval gates already exist. Lemo-Opuscar and Papermotion are the public examples.
Step 1
Separate style from shot
Lemo-Opuscar publishes STYLE.md files, a director guide, and sample scene code. The human picks a style, then approves keyframes, then approves the film.
Step 2
Keep physics and rigs in the engine
Papermotion is a paper-cut engine with deterministic physics, frame grabs, and sound checks. Later films inherit that engine even when the typed prompt is short.
Step 3
Do not hide the system
If a skill or a local repo did the work, say so. The Awesome index treats prepared systems as inputs, not as proof of a one-line miracle.
Tools
- https://github.com/lemomo-ai/lemo-opuscar
- https://github.com/francozanardi/papermotion
- https://github.com/buildwithhanif/claude-animation-skill
- https://github.com/klsoen/opus-js-animations
Checks
- Style file and scene file are in the repo
- Two approval points exist (storyboard, then film)
- License on code vs films is stated (Lemo uses MIT and CC BY 4.0)
In short
- Should I start from a blank HTML file?
- Only if you want to learn the path. For shipping, start from a system with a style sheet, a clock, and a render command.