Magistral launch
State the program's specific requirements first, then show continuously running output beside the code. Advance the entire composition around the same programming task.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Magistral launch · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#151515}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Motion and composition
Local motion · Composition rules
Break the long prompt into scannable requirements
Center the prompt box in a dark chat interface, organizing its body as items. Use monospace for code and ordinary sans serif for explanation; accent with an orange mark and a few colored balls.
Move from requirements to explanation and code
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Magistral launch · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#151515}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="0" data-end="29"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>After input finishes, shrink back into the chat layout and continue with segmented explanations. Move the camera downward with the current focus, retaining some preceding content to connect the reading sequence.
Give the running result a full side
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Magistral launch · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#151515}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="29" data-end="36.3"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Keep code on the left and show nine polygons on the right. Increasing side counts form a rule; ball colors distinguish individuals. Keep rotating or scaling shapes within their own cells.
Hold continuous motion long enough for viewers to see the relationship between boundaries, balls, and changes.
Choose another programming example
Use charts, layouts, or interactive components. Write visible requirements first, then choose matching result imagery; preserve prompt, explanation, code, and execution, without giving each equal time.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Replace with other programming tasks, but include a visual acceptance result.
- Polygon boundaries and ball motion jointly provide the validation view; keep all nine cells clearly separated.
Production constraints
Prompt / thinking paragraph / explanation / code / nine-cell polygon grid / colored balls
- Show specific constraints first, then explanations and code, and finally the running results side by side.
- Increase polygon side counts across cells, with balls moving inside their boundaries as visible validation.
- Pull back from the input close-up to chat, then push into the final two-column view.