Figma Specs and code layers: agents now read your design rules
Figma Specs and code layers hit open beta on October 15. Coding agents can now read your design rules over MCP. Write the rules down before they guess.
Figma shipped two features today that change who reads your design system. Figma Specs, a Markdown document that lives on the canvas, and code layers, real code prototypes next to your frames, both went to open beta on October 15. The point is simple: coding agents can now pull your written design rules and your working prototypes through Figma's MCP server. If your rules only live in one designer's head, the agent will guess. Agents guess wrong with confidence.
What actually happened
Per Figma's Specs announcement, Specs is a container for decisions, references and diagrams that sits in Figma or FigJam. You can drag an existing .md file onto the canvas to turn it into a spec, and embed frames or FigJam boards inside it. The Figma agent can answer comments in a spec and edit it on request. Through the Figma MCP server, coding agents can read a spec plus the frames, code layers and Code Connect snippets it links to. It is rolling out to paid plans.
Code layers let teams build interactive prototypes in code on the canvas. You can import a lightweight codebase from GitHub, capture a live page with Figma's Chrome extension, convert a design, or bring a prototype in from a coding tool over MCP. GitHub-linked layers can push to a branch and open a pull request. Code layers use AI credits, but creation and editing are free on paid plans through November 4, 2026.
Figma timed this with Config India. Its India post names Sarvam's Indus as a new MCP partner beside Claude Code, Cursor, GitHub Copilot and VS Code. TechCrunch quotes Figma's chief design officer saying teams now produce 17 times more code than before, but ship only 1.3 times more releases.
Why Figma Specs matters for your business
That 17x-to-1.3x gap is the whole story. Agents write plenty of code. Most of it misses the brief, because nobody wrote the brief down.
Write the spec first. Button states, spacing scale, what "primary" means, which components are off-limits. A one-page Markdown file beats a 40-frame library the agent has to interpret.
Keep it in the repo too. Specs is a Figma feature on paid plans. Your design rules should not depend on one vendor's beta. Keep the same .md in your codebase so Claude Code or Cursor can read it with or without Figma.
Use the free window. Code layers cost nothing on paid plans until November 4. Import one real screen from GitHub, let the agent change it, and review the pull request. You will learn in a week whether it saves time or makes cleanup.
Key takeaways
- Figma Specs and code layers entered open beta on October 15, 2026, for paid plans
- Coding agents can read specs and linked code layers through the Figma MCP server
- Code layers use AI credits but are free on paid plans through November 4
- GitHub-linked code layers push to a branch and open a pull request for review
- Keep your design rules as Markdown in your repo, not only inside Figma
Agents follow the rules you write down. Nothing else. We set up design specs, component rules and agent context files that live in your repo and work with any coding agent, so your product stays on-brand when the tool changes. See how we build it, or tell us what your team ships.
Sources: Figma: Introducing Specs, Figma: Code layers, TechCrunch.
- #figma
- #figma-specs
- #code-layers
- #mcp
- #ai-coding-agents
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
OpenAI retires GPT-4o and GPT-4.1 on January 14, 2027
OpenAI will shut off GPT-4o, GPT-4o mini, GPT-4.1, and GPT-4.1 mini snapshots January 14, 2027. Fine-tunes die with them. Here is the migration checklist.
Read itOctober 2026 Patch Tuesday: 1,411 flaws, patch the inbox first
Microsoft's October 2026 Patch Tuesday fixes a record 1,411 flaws, including an exploited Mark of the Web bypass. What a small team should patch first.
Read it