ııı motion.mdVideo style specification
Lovable / V041

Lovable · Start creating from Slack

Show multiple people contributing requirements, the assistant delivering results and the user confirming the next step within a single chat thread. Guide reading through the depth hierarchy of messages instead of splitting collaboration into unrelated screens.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 30.03 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>You can now tag @Lovable in Slack.

In a thread or DM, ask Lovable to build a new app, ship a change, or get quick answe · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#101013}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 elementsChat containerMessages from multiple participantsAssistant identityDashboardConfirmation reply
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Messages are the focus; the window is their container

Use a warm-to-cool gradient background and maintain high contrast on white message cards. Keep speakers, avatars and assistant markers consistently associated, so rearranging cards does not change their identities.

Use regular sans-serif text for message bodies and slightly heavier names; break long messages at natural semantic boundaries. Input and result cards should be more prominent than surrounding decoration.

02

Use depth to show conversational focus

After a new message enters the foreground, older messages recede slightly, scale down and lose contrast. Highlight only the message being read or a group of supplementary messages at a time, retaining enough context to show whom the assistant is answering.

Let the assistant respond once all participants have contributed. Show the result first and bring in follow-up questions afterward; when further action is involved, give the user's confirmation a separate beat.

Conversation stageInformation to communicate
Initial requestWhat needs to be done
Contributions from multiple peopleWhat data or conditions to add
Assistant deliveryWhat results have already been produced
Follow-up and confirmationWho approves the next step
Action feedbackWhat happened after confirmation
03

Results may change, but preserve thread relationships

Replace the feedback dashboard with a design proposal, campaign page or project plan, but also update the corresponding request and contributions from multiple people. Result names, follow-up questions and confirmation actions must connect coherently.

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 5.00 seconds
5.00s
Composition reference at 10.00 seconds
10.00s
Composition reference at 14.00 seconds
14.00s
Composition reference at 20.00 seconds
20.00s
Composition reference at 26.00 seconds
26.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • When adapting, preserve multiple contributions → assistant consolidation → results → confirmation
  • Avatars, business data and result types can be replaced, but speaker identities must remain consistent

Production constraints

Chat container / Messages from multiple participants / Assistant identity / Dashboard / Confirmation reply

  • Messages from different speakers enter the same thread, and the assistant responds after the request
  • Older messages recede and blur while new messages stay sharp in the foreground, using depth to express focus
  • Show usable results first, followed by follow-up questions and authorization, emphasizing continuity in collaboration