ııı motion.mdVideo style specification
Cursor / V260

Cursor Cloud Agents

Introduce product updates through brief claims followed by brief actions. Give each feature its own objects; unify the reading pattern, not interface content.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 43.87 seconds
Motion and composition example Open 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 Cloud Agents · 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>
Visual elementsExplanation on blackInteraction on whiteThread replyMode labelSubagent listGoal commandSummary checklist
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

One sentence on black, one example on white

Center the feature explanation on black in simple sans serif. Finish and hold the sentence for reading before cutting to the pale interface; contrast naturally creates chapter boundaries.

Reserve accents for mode labels, current commands, and status, avoiding a new decorative system for each feature.

02

Four features, four concrete actions

Show requests and confirmations for thread subscriptions, labels and later input for custom modes, independent work items for subagents, and goal commands with ongoing tasks for cross-turn goals. Do not turn every chapter into the same input box with different text.

Update directionCorresponding interaction view
Task subscriptionThread request and subsequent response
Custom modeMode label and input
Isolated subagentsMultiple independent task states
Persistent goalGoal command and subsequent work
03

Summarize only what has already been explained

Collect feature names into a final checklist, followed by the brand and update entry; do not add an undemonstrated fifth feature.

Rewrite other version updates with the same two-beat structure. Sentences may vary in length, but leave enough time to understand one action in each interaction segment.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 7.00 seconds
7.00s
Composition reference at 15.00 seconds
15.00s
Composition reference at 27.00 seconds
27.00s
Composition reference at 34.00 seconds
34.00s
Composition reference at 41.00 seconds
41.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • For changelogs, retain proposition→interaction evidence as two beats for each item
  • Replace the feature set, ensuring each claim matches the actual action that follows

Production constraints

Explanation on black / interaction on white / thread reply / mode label / subagent list / goal command / summary checklist

  • Present each feature as a one-sentence message on black followed by a short interaction on white, maintaining a regular rhythm
  • different features require subscription, mode, parallelism and target objects respectively rather than shared fake data
  • the closing list repeats demonstrated items without introducing new capabilities