The explanation for a screen often lives somewhere other than the screen. Figma’s answer is Specs: structured documents that sit alongside design work, so the rationale does not disappear into a separate handoff.
Announced on October 15, Specs uses Markdown and can reference frames, diagrams, and code layers. Through Figma’s MCP server, coding agents can read a linked spec with its associated context. Figma says the feature is rolling out in open beta on paid plans across web, desktop, and mobile. Its announcement describes the workflow.
Give decisions a visible home
Imagine a checkout redesign with three alternatives. Screens show how each version looks; the spec can record why one approach was chosen, what an engineer challenged, and which edge cases remain open. That is valuable context for the next person touching the flow.
The opportunity is a shorter distance between a decision and its implementation. The editorial caveat is familiar: putting a brief beside a frame will not keep it up to date automatically. A useful pilot would give one person responsibility for unresolved questions and compare the final build against both the design and the written requirements.
