ııı motion.mdVideo style specification
Vercel / V279

AI Gateway Virtual Models

Explain the capability in one sentence, then show a task-to-model mapping table or command. Avoid consecutive explanatory sentences; follow each concept immediately with a concrete usage example.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 41.07 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>AI Gateway Virtual Models · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#000000}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 elementsRelease copyTask-model mapping tableCommand lineConfiguration form
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Alternate brief statements and executable examples

Explain the capability in one sentence, then show a task-to-model mapping table or command. Avoid consecutive explanatory sentences; follow each concept immediately with a concrete usage example.

02

Distinguish hierarchy through brightness and type

Make the main sentence bright white and explanations gray; use monospace for stable paths, CLI, and values. Share column widths, brightening the changing row and dimming others.

03

Show updates as local field changes

Show updates as local field changesRule example
0.00 / 4.50 seconds
13–17.5 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>AI Gateway Virtual Models · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#000000}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="13" data-end="17.5"><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 the invocation entry unchanged while replacing model fields in the table; show mapping updates only after command typing finishes. Fixed left-side names clarify the stable entry.

04

Retain stable keys and variable values for a new theme

Adapt to routing, aliases, or configuration management. Replace commands and fields while preserving unified name—local update—all calls updated.

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 8.00 seconds
8.00s
Composition reference at 14.00 seconds
14.00s
Composition reference at 18.00 seconds
18.00s
Composition reference at 28.00 seconds
28.00s
Composition reference at 39.00 seconds
39.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Use actual target-product commands and fields, retaining the one-place-update narrative.

Production constraints

Release copy / task-model mapping table / command line / configuration form

  • Explain the capability in one sentence, then show a task-to-model mapping table or command. Avoid consecutive explanatory sentences; follow each concept immediately with a concrete usage example.
  • Make the main sentence bright white and explanations gray; use monospace for stable paths, CLI, and values. Share column widths, brightening the changing row and dimming others.
  • Keep the invocation entry unchanged while replacing model fields in the table; show mapping updates only after command typing finishes. Fixed left-side names clarify the stable entry.