Google Drive Connects to Figma agent
Bring external information into the design, then write the design changes back into a document. Use one revision to connect information access, design execution and an explanation of the change into a complete loop.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Google Drive Connects to Figma agent · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#161616}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
Keep the design canvas as the same object throughout

Establish the main design frame first, then enter a sourced request through the sidebar. Enlarge the canvas, input and citations in turn if needed, but keep the design title and key outlines recognizable rather than switching to another artwork.
Show the source before the revision
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Google Drive Connects to Figma agent · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#161616}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="4" data-end="24"><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>After the request, show retrieval and citations so viewers see the feedback before the corresponding components change. Keep revisions local and other design areas stable; result details should correspond to the feedback just shown.
Turn the design result into an explanatory document
Request a summary after confirming design details, then record what changed and why. After export completes, close on the connection statement and the two brands without introducing another task.
Dark outer frame, bright workspace
Place a light canvas and conversation area on a dark-gray background, using green, purple and orange for selection, emphasis and illustrative assets. Keep sans-serif headlines clear, with regular-weight citation and document text; place sources near the corresponding components where possible.
Preserve the read/write loop when changing repositories
Replace external files, feedback, design components and the summary document. Citations must explain the actual revisions, and the exported document must record those same changes; update connected-tool icons with the source and destination.
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 other repositories and design tools while preserving source → revision → record.
Production constraints
Design frame / Conversation sidebar / External files / Citation / Revise components / Summary document
- Read external feedback, make design changes, then produce a document recording the reasons for those changes, completing a read/write loop.
- Move between input, citations and canvas results while preserving the identity of the same design frame.