ııı motion.mdVideo style specification
xAI / Grok / V318

Grok Build | Project memory

Explain project memory through three concrete states: recording, browsing, and reading again. Place one explanatory sentence on the left and the corresponding terminal change on the right.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 14.29 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>Grok Build|Project memory · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#0c1518}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 elementsExplanatory headingTerminalMEMORY.mdMemory listReading state
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Give left and right distinct roles

Keep the black-teal texture low-contrast, using large white sans serif on the left and monospaced terminal text on the right. Keep terminal position and width constant while changing explanations by stage.

02

Give each state a visible action

Add a record while working; open the memory list and its content while browsing; in a later session, read the record before handling the related task. Keep filenames and core conventions consistent across stages.

StageTerminal content
RecordAdd a convention during a task
BrowseOpen the list and view the same convention
ReuseRead the convention in a new session, then continue the task
03

Clarify the session boundary

After browsing, establish the next session with a brief pause or a terminal content change. Show the existing record before expanding code or actions in the subsequent task.

04

Adapt to other accumulating knowledge

Replace with design conventions, project terminology, or team processes. Write one concrete piece of knowledge first, then plan its use in a later task; avoid scrolling unrelated text.

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 1.88 seconds
1.88s
Composition reference at 5.04 seconds
5.04s
Composition reference at 9.06 seconds
9.06s
Composition reference at 12.99 seconds
12.99s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to tools with persistent project knowledge; preserve the dependency between writing and reading next time.
  • Session changes are a conceptual boundary; do not imply memory within the same conversation turn.

Production constraints

Explanatory heading / terminal / MEMORY.md / memory list / reading state

  • Explain cross-session memory through three states: recording → browsing → later retrieval.
  • Keep the terminal on the right throughout, changing only one explanatory sentence on the left to reduce reading effort.
  • During reading, show references to existing records rather than random scrolling code.