Figma has launched Specs, a container for project context that lives directly on the Figma canvas. The feature is now rolling out in open beta to all plans and is available on web, desktop, and mobile.
Bringing Markdown onto the canvas
Markdown has become the de facto format for sharing context as more product builders collaborate with agents, but it carries limitations: files tend to be single player on local machines, relationships between documents are brittle, and little ties them back to the projects that produced them. Specs is built as a multiplayer container for the context that evolves into key project inputs and needs refinement over time.
Figma or FigJam users can create a spec by pressing D or selecting the Specs icon in the toolbar, and any .md file can be dragged onto the canvas to become one.
What a spec contains
A spec holds shared decisions and references canvas work such as diagrams, code layers, and designs. Figma-specific embedding lets a FigJam file, a frame, or any canvas node sit inline in the document, so text and designs appear side by side instead of as screenshots or stale links. Because the Figma agent can read and reply to comments, it can be treated as a collaborator on the same document as teammates.
External context can be pulled in through connectors. A technical spec can reference a codebase via the GitHub connector, or a team can select an open question in a PRD, add the Hex connector, and have the agent run an analysis, which leaves findings as a comment where the question was asked. Content dragged in from the canvas and later dragged back out retains its Figma properties.
A spec can also be duplicated on the canvas so each team member works on their own version in parallel before aligning on a direction.
Agents on both sides of the document
Specs sits inside a set of related agent capabilities: Figma MCP now reduces errors and token usage, agents can generate images, create code layers, and run Weave workflows, and 20 new integrations connect Figma to other tools. Content can be moved between forms — the Figma agent can turn a PRD into designs, prototypes, and code, or the reverse. For code layers, selecting Extract designs converts the current state back into editable design layers; the user chooses whether to bring over a single screen, a specific state, or a full flow.
When working from a coding agent, an architect or engineer can copy the spec's link and add it to a prompt. Through the Figma MCP server, agents like Codex read the spec and its linked context, including Markdown, frame and diagram references, code layers, and Code Connect snippets.
How teams are using it
Figma software engineer Noah Finer wrote a spec for the Specs feature itself: he mapped out guiding principles for edge cases, embedded FigJam diagrams to show flow, and shared it for comments. After finalizing it, he gave the spec and coworkers' comments to his agent via Figma MCP, updated the original spec through MCP as the code progressed, and had agents generate new FigJam diagrams to embed and send to reviewers.
Mark Harvey, staff product designer at Intuit, documents a new icon set for the Intuit Design System with a spec placed beside the icons. Each entry captures an icon's file name, category, search tags, and description. Figma researcher Mike Blight consolidates feedback from stickies, comments, and annotations into a spec after explorations, including open questions, to serve as a starting point for the next round. Figma software engineer Kat Busch organizes shareable work in a spec her agent reads as Markdown; when a feature's name changes, she prompts the agent to update the spec directly.
Agents can also help with review: since they can read and write comments in Specs, an agent can reply to every open comment with a suggested fix while teammates work in the same document, with each conversation in its own thread.



