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.
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>Motion and composition
Local motion · Composition rules
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.
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.
| Stage | Terminal content |
|---|---|
| Record | Add a convention during a task |
| Browse | Open the list and view the same convention |
| Reuse | Read the convention in a new session, then continue the task |
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.
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.
Sections and rhythm
Click a section to seek to it in the choreography example above.





Visual references · Discrete still frames
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.