ııı motion.mdVideo style specification
Linear / V240

Linear Agent — ask anything, command everything

Let the agent answer questions within the project context before moving to concrete action results. Move between the project, evidence and conversation rather than repeatedly changing work settings.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 54.85 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>Linear Agent — ask anything, command everything · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#090a0c}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 elementsProject containerAgent conversationKnowledge documentRelationship diagramResults list
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Make the project a stable background first

0.00s · Composition reference

Establish the project container before moving to agent input and answers. Keep the angled composition facing the same direction; retain the project title or part of the sidebar when moving closer to the active area to show that the conversation belongs to the same workspace.

02

Show evidence after the follow-up question

Show evidence after the follow-up questionRule example
0.00 / 25.00 seconds
13–38 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>Linear Agent — ask anything, command everything · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#090a0c}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="13" data-end="38"><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>

Move from the answer list into a follow-up question, then show the project description and relationship view. Documents provide content evidence and diagrams provide connection evidence; keep the current question and relevant material near one another as the camera changes views.

03

Move from answers to real actions

Pull back to the workspace overview before showing the action-results list. Reveal results after their related questions, answers and evidence, using stable completed states before closing on the product statement.

04

Separate depth through light and dark

Build hierarchy with a black-gray background, brighter work panels and local cool-purple accents. Use medium-bold sans-serif headlines and regular-weight list and document text; angles and depth of field should support focus without making content unreadable.

05

Adapt to another project system

Replace the project, knowledge materials, questions and action results with content from the same business. Match diagram nodes and document names to actual project objects, and let the final results list answer the opening task.

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 13.00 seconds
13.00s
Composition reference at 25.00 seconds
25.00s
Composition reference at 30.00 seconds
30.00s
Composition reference at 43.00 seconds
43.00s
Composition reference at 52.00 seconds
52.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to another product-management system while preserving context → question → evidence → action result.

Production constraints

Project container / Agent conversation / Knowledge document / Relationship diagram / Results list

  • Move an angled camera between the project and agent, using documents and relationship diagrams as evidence for the answers.
  • List completed actions at the end to emphasize the progression from questions and answers to execution.