Figma Specs
Organize requirements, designs, rules and discussions into implementation specifications that can be handed off. Gradually structure scattered material before passing it to an agent.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Figma Specs · 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
Establish material hierarchy through different content formats

Show the requirements document first, then introduce data, rules tables, code blocks and comments. Preserve each format's role: tables support comparison, code supports locating details, and comments attach to the area being discussed.
Let collaborative revisions change the organization
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Figma Specs · 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="15" data-end="28"><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>Reorganize content after comments, then place design frames beside their explanations. Keep major headings during reordering so viewers recognize the same requirements; place designs near the relevant explanations to reduce searching across the frame.
Generate the handoff specification only after organization is complete
Reveal the specification once the relationship between documents and designs is clear, then show the agent using it. Allow higher information density early on, narrowing the handoff to a title, key constraints and a clear entry point.
Let document hierarchy define the visual style
Place light document panels inside a dark-gray outer frame, limiting green, purple and orange to local selections and creative accents. Distinguish sans-serif headings and body copy by weight, using monospace for code; give tables, design frames and comments their own boundaries instead of crowding one information layer.
Reorganize the material when changing requirements, rather than only renaming the title
Replace business goals, rules, designs and code examples, then let comments drive a meaningful revision. The final specification should explain decisions formed from the earlier material, while the agent entry point retains the same task name.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Change the requirement type while preserving evidence gathering → collaborative revision → implementation handoff.
Production constraints
Requirements document / Rules table / Code block / Comment / Design frame / Implementation specification
- Bring business, design and code evidence together in a document, use comments to drive reorganization, and finally turn it into an actionable implementation handoff specification.
- Place design frames beside their explanations to show what belongs together without losing source context.