Archival Fragments
Create a complete short film from scratch. The user may give you only an idea or a finished script—both follow the workflow below.
Three hard constraints (violating any one of them will ruin the final film)
1. Every shot must have a different image
N shots require N+1 distinct keyframes.
“S sharing the same image between two adjacent shots” means: the first shot’s end frame = the second shot’s start frame, so that one image is shared by both shots.
It does not mean using one image for the entire film.
Absolutely prohibited:
- Using the same image as the input for every shot
- Using a single structural diagram, schematic, or infographic as the reference for every shot
- Using
assets/style-reference.png
as a generation input—it is a style reference board for humans and must never be attached to any generation request
A film made this way has dozens of shots that all look exactly the same, as if the shots had never been broken down. Viewers will swipe away within three seconds.
Self-check (mandatory; report the results to the user):
Keyframe count == shot count + 1 ✓/✗
No two keyframes have identical image descriptions ✓/✗
Every keyframe has its own independent prompt ✓/✗
2. You must break down the story, visuals, and rhythm yourself, and present the breakdown for the user to review
Do not begin generating immediately after receiving the script. You must first produce a shot-by-shot table containing each shot’s narration, visual content, start and end frames, and duration. Present it to the user for review so they have a chance to reject or revise it—changing a table takes 5 minutes, while rerunning the entire production after changes takes 4 hours.
See 01-script.md for details.
3. Favor concrete imagery over abstract graphics
The paper and red lines are the visual foundation, not the subject. For every sentence, find a universal symbol that viewers can understand without thinking—a world map with a pushpin, a set of scales, steps, a large pile of physical objects, and so on. A film should converge on 2–3 symbols, using each several times.
Using blank paper with a line to represent “this position is empty,” or using three squares to represent “three companies”—these abstract graphics are difficult for viewers to understand and have failed in real-world testing.
See Rule 0 in style-guide.md for details.
Workflow
Proceed in order. Each stage has its own document:
| Stage | Document | Output |
|---|
| 0. Environment preparation | 00-setup.md | Dependencies installed, credentials available, all checks passing |
| 1. Idea → script → story/visual/rhythm breakdown | 01-script.md | + shot-by-shot table |
| 2. Design the keyframe chain | 02-keyframes.md | |
| 3. Write motion sentences | 03-shots.md | |
| 4. Arrange the rhythm | 04-rhythm.md | Shot-duration allocation table |
| 5. Generation and assembly | 05-produce.md | Keyframes → shots → voiceover → final film |
Consult style-guide.md at any time for the visual baseline.
Three checkpoints where you must stop and ask the user:
- After completing the Stage 0 checks—tell the user the environment is ready and ask for an idea or script
- After completing the Stage 1 breakdown—present the shot-by-shot table for the user to review
- After Stage 5 has produced 2–4 samples—confirm the direction before running the full production
Default parameters
4:3 / 2K (1920×1440) / Video:
/ Images:
/
/ 5 seconds per generated shot /
Concurrency limit: 1; generation must run serially.
What’s included
- — six rule documents corresponding to the stages in the table above
- — the complete configuration for a finished 67.3-second film: 35 original keyframe prompts, 34 motion sentences, a shot-duration allocation table, 17 narration lines, and the script. Follow the structure, but do not copy the content—those symbols were designed for a specific subject
assets/style-reference.png
— a style reference board for human viewing only
assets/example-01..08-*.jpg
— eight consecutive keyframes showing how the visuals advance one frame at a time within the same film