---
type: "post"
id: "look-ma-we-re-famous-analysis-6cba07"
slug: "look-ma-we-re-famous-analysis-6cba07"
title: "Look ma we're famous!"
description: "Thesis: Design tools are turning their canvases and system rules into context surfaces that coding agents can consume, rather than treating design as a static handoff artifact."
retrieval_nugget: "Thesis: Design tools are turning their canvases and system rules into context surfaces that coding agents can consume, rather than treating design as a static handoff artifact."
published_at: "2026-10-19"
updated_at: "2026-10-19"
record_date: "2026-10-19"
date_kind: "published_at"
topics: ["mcp","coding-agents"]
source_urls: ["https://www.figma.com/blog/build-by-design/"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:look-ma-we-re-famous-analysis-6cba07"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:7ae3f346a7b8b325839bf4ad6d5f51af1ca9bb7e517f737e317caebe84f07877","reviewed_at":"2026-10-19T20:07:41.592Z","source_evidence_count":1,"verified_claim_count":3,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":3,"implication_count":2,"watch_condition_count":1,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Design tools are turning their canvases and system rules into context surfaces that coding agents can consume, rather than treating design as a static handoff artifact.","observed_facts":[{"text":"Figma’s October 15, 2026 post says code layers entered open beta on all plans, enabling teams to explore code-backed prototypes on the canvas.","source_urls":["https://www.figma.com/blog/build-by-design/"]},{"text":"It says design-system guidelines entered open beta and code sources from GitHub repositories or npm packages began in closed beta on paid plans.","source_urls":["https://www.figma.com/blog/build-by-design/"]},{"text":"A separate supplied announcement says Figma is partnering to bring Figma to Delta and Zed via MCP, but gives no capability or rollout details.","source_urls":["https://www.figma.com/blog/build-by-design/"]}],"mechanism":"Figma describes Specs as a shared context container that can reference decisions and work across diagrams, designs, and code layers; its MCP server can send that context to coding agents. The practical change is a more structured handoff: agents can be given reusable design rules and code sources, while teams inspect code-backed results in the design environment.","why_now":"The announcement explicitly frames these launches around teams increasingly building with agents, when producing prototypes is easier but preserving shared context and collaboration is harder.","implications":["Design-system rules and code sources can become inputs to agent work, potentially reducing drift between generated interfaces and a team’s established patterns.","The MCP partnership also suggests that this context may move across more than Figma’s own interface, though the named integration’s exact scope remains unreported."],"evidence_boundary":"The supplied Figma blog is a company description of its products and availability. The separate partnership announcement names Delta, Zed, and MCP only; it does not establish supported operations, rollout dates, or whether all Figma features are exposed. This evidence supports a product-direction reading, not a measured claim about quality or adoption.","watch_conditions":["Look for documentation specifying which Figma objects and actions Delta and Zed can access through MCP, and whether design-system guidelines and code sources are available to those integrations."],"related_records":[],"new_branch_reason":"No prior New Runtime record was supplied for this specific MCP partnership and its connection to Figma’s newly described context workflows."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/look-ma-we-re-famous-analysis-6cba07/","markdown":"https://newruntime.com/posts/look-ma-we-re-famous-analysis-6cba07.md","json":"https://newruntime.com/posts/look-ma-we-re-famous-analysis-6cba07.json"}
related_patterns: ["design-systems-become-agent-context"]
---

# Look ma we're famous!

## Retrieval answer

Thesis: Design tools are turning their canvases and system rules into context surfaces that coding agents can consume, rather than treating design as a static handoff artifact.

Thesis: Design tools are turning their canvases and system rules into context surfaces that coding agents can consume, rather than treating design as a static handoff artifact.

Observed facts: Figma’s October 15, 2026 post says code layers entered open beta on all plans, enabling teams to explore code-backed prototypes on the canvas. It says design-system guidelines entered open beta and code sources from GitHub repositories or npm packages began in closed beta on paid plans. A separate supplied announcement says Figma is partnering to bring Figma to Delta and Zed via MCP, but gives no capability or rollout details.

Mechanism: Figma describes Specs as a shared context container that can reference decisions and work across diagrams, designs, and code layers; its MCP server can send that context to coding agents. The practical change is a more structured handoff: agents can be given reusable design rules and code sources, while teams inspect code-backed results in the design environment.

Why now: The announcement explicitly frames these launches around teams increasingly building with agents, when producing prototypes is easier but preserving shared context and collaboration is harder.

Implications: Design-system rules and code sources can become inputs to agent work, potentially reducing drift between generated interfaces and a team’s established patterns. The MCP partnership also suggests that this context may move across more than Figma’s own interface, though the named integration’s exact scope remains unreported.

Evidence boundary: The supplied Figma blog is a company description of its products and availability. The separate partnership announcement names Delta, Zed, and MCP only; it does not establish supported operations, rollout dates, or whether all Figma features are exposed. This evidence supports a product-direction reading, not a measured claim about quality or adoption.

Watch condition: Look for documentation specifying which Figma objects and actions Delta and Zed can access through MCP, and whether design-system guidelines and code sources are available to those integrations.

This is a distinct analytical record because no prior New Runtime record was supplied for this specific MCP partnership and its connection to Figma’s newly described context workflows.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Mcp](https://newruntime.com/topics/mcp.md): Explore the mcp topic hub.
- topic hub: [Coding Agents](https://newruntime.com/topics/coding-agents.md): Explore the coding-agents topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)