ııı motion.mdVideo style specification
Rive / V384

Rive CLI — build Rive files with your agent

Demonstrate interaction through works that genuinely change state, with games, controls, design systems and a sequencer each showing one clear action.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 31.27 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>Rive CLI — build Rive files with your agent · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#070909}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 elementsRace trackRhythm arrowCard columnGlass controlKnobEditorStep cell
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Let viewers see an action before changing works

Give racing forward speed, rhythm games hit feedback, and cards position changes. Let each work occupy its own screen instead of shrinking all into simultaneous tiles.

02

Unify different visual languages with a black outer stage

Allow different palettes and fonts while retaining black margins. Keep status figures, selection colors, and results bright enough, preventing dark control bases from swallowing edges.

03

Connect sequencer-cell feedback through a scanning line

Connect sequencer-cell feedback through a scanning lineRule example
0.00 / 3.20 seconds
25.6–28.8 seconds · Motion 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>Rive CLI — build Rive files with your agent · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#070909}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="25.6" data-end="28.8"><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>

Fix column width and row spacing, using lit cells for programmed steps and a uniformly moving playhead. Briefly brighten active cells as it passes, leaving empty cells unchanged.

04

Preserve visible interaction causality when changing examples

Replace with different apps, giving every screen input, state, and feedback. Share outer framing without forcing internal work into one style.

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 6.00 seconds
6.00s
Composition reference at 13.00 seconds
13.00s
Composition reference at 17.00 seconds
17.00s
Composition reference at 25.57 seconds
25.57s
Composition reference at 31.00 seconds
31.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Replace with different apps, giving every screen input, state, and feedback. Share outer framing without forcing internal work into one style.

Production constraints

Race track / rhythm arrow / card column / glass control / knob / editor / step cell

  • Demonstrate interaction through works that genuinely change state, with games, controls, design systems and a sequencer each showing one clear action.
  • Give racing forward speed, rhythm games hit feedback, and cards position changes. Let each work occupy its own screen instead of shrinking all into simultaneous tiles.
  • Allow different palettes and fonts while retaining black margins. Keep status figures, selection colors, and results bright enough, preventing dark control bases from swallowing edges.