ııı motion.mdVideo style specification
Manus / V046

Turn repetitive work into automated tasks

Explain automation through explicit conditions and actions. Configure when something should happen first, then use notifications and results to prove that the task progressed.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 27.03 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>Turn recurring work into automated tasks · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f8f6}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 elementsTrigger conditionActionConnecting arrowPhone notificationResult card
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Two columns express causality

Write the trigger on the left and action on the right, retaining concrete subjects, conditions, and outcomes in short phrases. Connect condition to action rather than treating the panels as independent feature cards.

Use a light background, white panels, and few accents. WHEN and THEN can be slightly heavier, with conditions in regular sans serif. Wrap long conditions rather than shrinking them into dense small text.

02

Show notifications only after setup is complete

Enter the condition, then the action, and confirm; afterward cut to the phone notification or task result. Result text must correspond directly to the condition. The notification says it was triggered; give the full output separate reading space.

Example conditionCorresponding action wording
Price falls below a thresholdNotification identifies the item and price
A category of information is updatedProduce the corresponding summary or list
A specified event occursPerform a concrete task and return the result
03

The same structure supports different work

Reuse the two-column layout in the second example, changing only condition and action to avoid repeated instruction. Rewrite notifications, results, and conditions together, retaining setup→trigger→delivery.

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 4.00 seconds
4.00s
Composition reference at 6.53 seconds
6.53s
Composition reference at 11.00 seconds
11.00s
Composition reference at 14.00 seconds
14.00s
Composition reference at 23.00 seconds
23.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Preserve if X happens→do Y→report the result when adapting
  • Triggers must be specific and testable, and results must match actions

Production constraints

Trigger condition / Action / Connecting arrow / Phone notification / Result card

  • Show conditions and actions in pairs, and execute only after both are filled in
  • configure on desktop and deliver results through phone notifications, distinguishing configuration time from trigger time
  • use the same two-card structure for different scenarios later