Figma Specs carries team decisions and design context to coding agents
Figma has begun rolling out Specs, a shared document space that combines Markdown text with design elements on its canvas. Teams can keep decisions beside the frames, diagrams and code they describe, then pass that context to coding agents. The open beta is intended to connect planning with implementation across paid plans.
Artificial Intelligence··Evening
A shared document joins the canvas
Design-software company Figma introduced Specs, a Markdown-based document space for decisions and design context shared by people and coding agents. Text can sit alongside the design elements it describes, giving teams a common reference for implementation.[1], [2]
Figma says the open beta began rolling out to paid plans on October 15 across web, desktop and mobile. Existing Markdown files can become Specs documents by dragging them onto the canvas. A document can embed FigJam diagrams, design frames and code layers.[1]
Discussion stays beside the decisions
Team members can duplicate a document to explore different directions before agreeing on a plan. Figma’s agent can read and answer comments within it, with each discussion kept in its own thread. The company gives examples of drawing codebase context from GitHub and asking the Hex data-analysis connector to examine product data and leave its answer in a comment.[1]
Coding agents receive the linked context
Coding agents can read Specs text and its linked frames, diagrams and code snippets through Figma’s Model Context Protocol server, a connection that gives external tools access to that material. A team can pass a Specs link into its implementation request. Figma presents these as workflows for carrying design decisions forward, rather than measured reductions in development time or errors.[1]
