Figma 推出 Specs——画布上的多人 Markdown 容器，公开测试面向付费档，Codex 这类 agent 可经 Figma MCP server 读取，code layers 进入公开测试

“Figma 的新功能 Specs 把你的 Markdown 变成画布上的多人容器——拖进任何 .md 文件，Codex 这类 agent 就能经 MCP server 读它（公开测试、付费档）。”

可用说法

• 2026 年 10 月 15 日（页面 JSON-LD datePublished 为 2026-10-15T04:51:00Z），Figma 宣布推出 Specs。按 Figma 博文：「We're launching Specs, a container for your context that lives on the Figma canvas.（我们正在推出 Specs——一个住在 Figma 画布上的、装你上下文的容器。）」——「Turn existing Markdown into a spec by dragging and dropping any .md file onto the canvas.（把任何 .md 文件拖放到画布上，就能把现有 Markdown 变成一份 spec。）」——「Today, more and more product builders are working in Markdown, as collaborating with agents becomes more standard. It's the de facto format for sharing context.（今天，随着与 agent 协作成为常态，越来越多的产品构建者在用 Markdown 工作。它是分享上下文的事实标准格式。）」定位：「That's why we built Specs: a multiplayer container that allows context to fully express itself and move into, out of, and across Figma.（所以我们造了 Specs：一个多人协作的容器，让上下文得以充分表达，并进出、横跨 Figma。）」创建：「To create a spec, just press 'D' on your keyboard or click the Specs icon in the toolbar in Figma or FigJam.（要创建 spec，只需按下键盘上的 D 键，或在 Figma 或 FigJam 工具栏点击 Specs 图标。）」agent 协作：「And since the Figma agent can read and reply to comments, you can collaborate with the agent the same way you would with a human collaborator.（由于 Figma agent 能读取并回复评论，你可以像与人类协作者共事那样与这个 agent 协作。）」MCP 一侧：「MCP now reduces errors and token usage so teams can move faster and more efficiently.（MCP 现在能减少错误与 token 消耗，让团队更快、更高效。）」——「20 new integrations bring Figma context and capabilities into more of your tools.（20 个新集成把 Figma 的上下文与能力带进你更多的工具。）」——「Through the Figma MCP server, agents like Codex can read a spec and see all of the context it links to.（通过 Figma MCP server，Codex 这类 agent 能读取 spec 并看到它链接的全部上下文。）」可用性：「Specs is available on web, desktop, and mobile, rolling out in open beta to paid plans starting today.（Specs 覆盖网页端、桌面端与移动端，自即日起以公开测试形式向付费档推出。）」按 TechCrunch（Ivan Mehta，发稿 10 月 14 日晚 9:30 PDT，正值「the company's first Config event in India（该公司在印度的首届 Config 大会）」）：Figma 推出了「Figma Specs, which is a markdown editor that lets users define their design language in a simple way（Figma Specs——一个让团队用简单方式定义设计语言的 markdown 编辑器）」，Specs「can exist as a standalone file in Figma or can co-exist within the canvas（既可以作为 Figma 里的独立文件存在，也可以在画布中共存）」；「Figma also made its code layers feature available to users in open beta（Figma 还将 code layers 功能以公开测试形式开放给用户）」——「The company announced this feature in private beta back in June.（该公司早在 6 月就宣布过这一功能的私密测试。）」；其 MCP「supporting over 20 new tools with its MCP, including Open Code, Dia, Grok Bot, and Indian AI startup Sarvam（正通过 MCP 支持超过 20 个新工具，包括 Open Code、Dia、Grok Bot 与印度 AI 创业公司 Sarvam）」。首席设计官 Loredana Crisan 告诉 TechCrunch：「We see Figma as the place where software teams come to decide what they build and ship. And so for that, I think one of the key things to keep in mind about what AI has changed and what it made available is the ability to build,（我们认为 Figma 是软件团队决定构建什么、发布什么的地方。正因如此，我认为关于 AI 改变了什么、让什么成为可能，要记住的关键一点是构建的能力，）」——以及她的收尾段：「There are 17-times more lines of code being produced today than in the past. But when you're looking at releases, only 1.3-times more releases. A lot of that code actually is not necessarily built to ship, but really built to discover what the product is. It's built to design.（如今的代码行数约为过去的 17 倍。但看发布数量，只约为过去的 1.3 倍。其实很多代码未必是为了发布而写，而是为了探索产品是什么。它是为设计而写的。）」