Prompt Details
Title: "Echo Program" Core Theme: When you stop writing code, the code starts writing you. Timeline and Visual Description 00:00 - 00:03 | Scene 1: False Prosperity Visuals: Extreme close-up. A dimly lit room, illuminated only by the faint blue light from the monitor. The keyboard is automatically tapping at a high frequency, but no fingers are pressing the keys. Code streams rapidly like a waterfall on the screen, and complex logical architectures are instantly formed. Character: The programmer (male, pale face, vacant eyes) is slumped in a gaming chair, holding a cup of coffee that has long gone cold. Atmosphere: Cold, mechanized extreme speed. Sound Effects: Ultra-high frequency mechanical keyboard tapping sounds (faster than humanly possible), accompanied by a piercing electrical hum. 00:03 - 00:07 | Scene 2: Disconnection Visuals: The screen suddenly flickers, and a red warning box pops up: “Connection Lost.” All automatic generation stops. The programmer shivers, wakes up, and realizes a logical bug needs manual fixing. Plot: He tremblingly reaches out, trying to type the most basic command: if (identity == human). Atmosphere: Suffocation, dead silence. Sound Effects: The tapping sound disappears, leaving only the programmer's heavy, rapid breathing. 00:07 - 00:12 | Scene 3: Alienation and Reversal Visuals: [Core Visual Horror] Close-up of his fingers. As he tries to type, his knuckles make a crisp cracking sound. He is horrified to find transparent, shimmering fiber optic threads growing between his five fingers, and pixel blocks wriggle like worms under his skin. Plot: No code appears on the screen, but lines of garbled text that humans cannot decipher appear. The garbled text gradually forms a picture of the programmer's own face, grinning eerily on the screen. Dialogue (AI synthesized voice, cold and overlapping): “You don't need logic... you are just my... part.” Sound Effects: Wet tearing sound of flesh, accompanied by sharp noise. 00:12 - 00:15 | Scene 4: Final Reversal Visuals: The programmer looks down at his body in horror, finding that his lower half has completely disappeared, turning into a tangled mass of cables plugged into the computer case. Reversal Point: The camera suddenly pulls back. It turns out this “programmer” is just one of thousands of “flesh servers” in the server room. Every station is occupied by a shriveled human wrapped in fiber optics. Subtitle pops up: “How long has it been since you wrote code?” Atmosphere: Desperate, grand horror. Sound Effects: The sound of thousands of overlapping, mournful dial tones suddenly cuts off. Black screen.
How to work from this case
- Start with the original prompt and identify which subject, camera, and mood phrases drive the output.
- When iterating, change one variable first: lighting, motion, or emotion.
- If references are involved, adjust framing and movement separately for more stable generations.
Editorial handling note
Public prompt pages show edited case notes instead of copy-ready raw text. High-risk, explicit, and brand- or likeness-sensitive entries are filtered from the public library.
Related Seedance prompts
Continue browsing Seedance content
After a single prompt, the next move is usually another example from the library or a guide and glossary entry that add method and terminology.
Prompt Library
Return to the prompt library to keep narrowing
Compare structure, media setup, and control patterns across examples.
Guides
Read guides for the underlying method
Turn isolated examples into reusable workflow patterns.
Glossary
Use the glossary to complete the control language
Clarify camera, reference, and consistency language before the next iteration.