Cursor Builds — cloud agents start 3x faster
Use a simultaneous before-and-after comparison for speed, then a local failure for recovery. Explain “faster” and “easier to resolve problems” separately.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Cursor Builds — cloud agents start 3x faster · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f5f5f1}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
Start both at the same moment
Match Before and After window sizes and baselines, starting timers together. Progress may differ, but compare the same kind of work without hidden differences in starting conditions.
Support both interfaces with a pale background and distinguish them through warm color and green. Use clear sans serif labels, aligned seconds, and readable completion states; use dark completion text on pale backgrounds.
Keep the old workflow visible after the new one finishes
Show a usable interface or completion mark on the right while the left continues its own progress. Hold both briefly so the difference is directly visible before switching capabilities.
Give a next step when failure occurs
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Cursor Builds — cloud agents start 3x faster · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f5f5f1}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="9" data-end="15"><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>Show a failed local build item while retaining completed ones. Push into Debug with Agent or the equivalent repair entry, then indicate continued handling after clicking; do not erase errors to manufacture total success.
Rebuild comparison conditions for a new example
Use the new task's actual start, completion criteria, and durations. Reuse dual windows and progress bars, but align speed claims with displayed evidence; retain a clear error and actionable entry in the recovery segment.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- For performance comparisons, use a fixed start and equal workloads
- Comparison figures must be measured; the example's speedup only repeats the original claim
Production constraints
Before-and-after windows / independent timers / build steps / success box / error message / debug button
- Start both groups simultaneously but advance them at different speeds, with the new workflow showing results first
- then acknowledge a local failure and provide a debug button rather than claiming every task succeeded
- explain speed and recoverability in separate sections rather than combining them into one number