Figma Just Moved the Rulebook Into the Library: Design News Digest, Week of Oct 19, 2026
Intro: The Week Design Rules Became Computable
There’s a question underneath every conversation about AI in product design: how does an agent learn to design well? Historically the answer has been fuzzy — README files, Slack threads, a senior designer’s memory, and a lot of hopeful prompting. This week, the answer got concrete.
On Oct 15, 2026, Figma announced the Config India 2026 releases under a “build by design” framing, backed by the corresponding release notes entry. Buried in the feature list is a structural shift that matters more than any individual feature: Figma is moving design rules — Guidelines, system checks, code sources — out of tribal knowledge and INTO the published library, where the Figma agent can read them at generation time.
That’s the through-line for this digest. Instead of asking “what shipped?”, we’re asking one question of every item: does this make design intent machine-readable? Nine days earlier, on Oct 6, 2026, The Figma agent had already gone generally available, and per-library Guidelines were part of that story. The Config India releases are what happen next: the rulebook itself becomes a first-class artifact inside the design tool.
If you maintain a design system, the actionable lesson is simple: write the rule on the component it governs. That’s now the surface agents actually read.
The Anchor: Figma Config India 2026
Config India 2026 is the anchor event for the week, dated Oct 15, 2026. The official build by design post from Dylan Field sets the framing, and the release notes for Oct 15 carry the item-by-item detail, including the roundup entry “Here’s everything from Config India 2026.”
Two dates matter for the timeline. The agent itself had already exited beta on Oct 6, 2026 (The Verge). Config India, nine days later, is where the substrate the agent works on got its upgrades.
What Shipped
Code Layers: The Agent’s New Substrate
Code layers (open beta on all plans) and Specs were covered in depth in the October 15 digest. The part that matters for this digest: a code layer is a surface where design and implementation are the same object, so the rules an agent reads have to point at real code and real components.
Guidelines: Rules Written Where Agents Read Them
This is the centerpiece of the week’s structural argument. Guidelines are in open beta on all paid plans, and the mechanism is worth stating precisely: they are markdown rules attached to published design libraries, and the agent reads them when the library is enabled (Figma’s agent and design systems post; also noted at agent GA via The Verge).
The rules live on the library, not in a doc somewhere. They’re plain markdown. And they’re read at generation time — when the agent has the library enabled — not summarised once at training time.
Practically, this is the difference between a design system that a human reads and a design system that a machine executes. If your guidance says “cards use a 12px radius and never a shadow on mobile,” that sentence now has a home where the agent will encounter it.
Code Sources, System Map, and System Checks: The Rest of the Stack
Three more pieces complete the stack, at three maturity levels:
Code sources are in closed beta. The idea is to import code from GitHub repos or npm packages so agents build against your real components rather than approximations of them. Closed beta means access is gated; treat it as a watch item, not a today item.
System map (centralized design systems — libraries, changes, and dependencies in one place) is preview only per the release notes. Preview means the shape is visible but the surface isn’t dependable yet.
System checks are the audit arm, and Figma published a sample report to make the output concrete: 12 component issues and 10 token issues, with the scan’s examples of gaps being a missing description and a missing interactive state (build by design post). Those two examples are the kind of gap that stays invisible until someone writes the rule down.
The Agent Stack Around It
The surrounding platform moved too, and it’s what makes the library-as-rulebook idea viable.
The Figma agent went GA on Oct 6, 2026 (The Verge), with guidelines configurable per design library, custom skills on Starter, and the agent using AI credits as of Oct 6 per the release notes. Figma’s own three product-designer workflows for the agent show it in use.
Gemini 4 Argon began rolling out in Figma Make on Oct 13, 2026, across all plans (release notes).
Payload in Make: Make now scaffolds a Payload backend (CMS, database, media, APIs, auth, admin panel), rolling out across all plans, per the Payload team joining Figma.
Figma MCP is faster with support for more Figma products, plus 20 new MCP partner integrations including Dia, Junie by JetBrains, Meta Muse, and OpenCode (release notes). Figma’s MCP server now also generates code layers and works with Specs, so the same library reaches outside tools too.
Adjacent News: Figma Motion and JPEG XL vs AVIF
Not everything this week serves the machine-readable thesis.
Figma Motion has been in open beta since Sep 30, 2026 (release notes). It brings custom animation styles — custom easing, duration, and variable-backed properties, publishable to libraries — plus audio on the timeline with MP4/WebM export, per-character/word/line text animation that stays editable, and export as Lottie or dotLottie. One quiet detail fits our thesis: publishable, variable-backed animation styles are tokens for motion. But Motion is, today, adjacent rather than central.
Jake Archibald on JPEG XL vs AVIF (Oct 15, 2026) is a side note: AVIF wins for most web images, with JPEG XL coming in roughly 15–25% larger for lossy photos and 30–90% larger for screenshots and illustrations at default effort (jakearchibald.com), as summarized in Art Direction Daily. The numbers come from that secondary summary and are reported here, not re-verified.
The DTCG Question: Where’s the Token Spec in All This?
Design system people will immediately ask: does any of this change the token spec? The honest answer this week is no. The Design Tokens Community Group shipped its first stable spec, 2025.10, on Oct 28, 2025, backed by 40+ organizations including Adobe, Figma, Google, Microsoft, Shopify, and Salesforce, per a secondary overview (CODERCOPS). No new DTCG release is verified for October 2026, and we’re not going to invent one.
Feature × Status Snapshot
| Feature | Status | Plans | Shipped |
|---|---|---|---|
| Figma agent | GA | — | Oct 6, 2026 |
| Figma Make on Gemini 4 Argon | Rolling out | All plans | Oct 13, 2026 |
| Code Layers | Open beta | All plans; free create/edit on paid plans through Nov 4 | Oct 15, 2026 |
| Specs | Open beta | Paid plans | Oct 15, 2026 |
| Guidelines | Open beta | All paid plans | Oct 15, 2026 |
| Code Sources | Closed beta | — | Oct 15, 2026 |
| System Map | Preview | — | Oct 15, 2026 |
| Figma Motion | Open beta | — | Sep 30, 2026 |
| DTCG token spec | Stable (2025.10) | — | Oct 28, 2025 |
Sources for the rows above: release notes, Specs announcement, The Verge on agent GA, and Figma’s agent and design systems post.
Sourcing Gap
Figma Make’s GA status rests on one secondary source, so this digest does not state it as confirmed. The Gemini 4 Argon rollout to all plans on Oct 13 is confirmed in the release notes.
The Bottom Line
Verdict: the library is becoming the contract.
For years, a design system’s real value lived in the parts that couldn’t be versioned — the reasoning, the exceptions, the “we don’t do it that way because…” This week, Figma moved that reasoning into an artifact the agent reads at generation time. Guidelines are markdown on published libraries. Specs are context next to the design. Code sources point agents at real components. System checks tell you which parts of the contract you forgot to write down — with Figma’s own sample report surfacing 12 component issues and 10 token issues, and checks that look for gaps such as missing descriptions and interactive states (build by design post).
The reader lesson stands: if you maintain a design system, author Guidelines, component descriptions, and interactive states on the components they govern. Not in a Notion doc. Not in the team wiki. On the library — because that’s now the surface agents actually read.
FAQ
1. What’s the difference between Guidelines, Specs, and Code Sources in Figma’s new stack? They sit at three different layers of intent. Guidelines are markdown rules attached to a published design library, read by the agent when the library is enabled (Figma’s agent and design systems post) — they govern behavior. Specs are markdown documents that can reference designs, code layers, and diagrams (Specs announcement) — they explain intent and context. Code sources import real components from GitHub repos or npm packages (release notes) — they give the agent ground truth to build against.
2. Do I need a paid plan to use any of this? It varies. Code Layers are open beta on all plans, with creating and editing free on paid plans through Nov 4 (release notes). Specs are open beta on paid plans (Specs announcement). Guidelines are open beta on all paid plans (release notes). Code Sources are in closed beta, intended for all paid plans.
3. How do I write Guidelines an AI agent will actually follow? Write them as markdown rules, on the published library, attached to the specific components they govern. Per Figma’s agent and design systems post, the agent reads these when the library is enabled — so proximity to the component is the whole game. Then publish the library, and run system checks to find the components still missing descriptions or interactive states (release notes).
4. Is there a new design tokens spec this week? No. No new DTCG release is verified for October 2026. The latest stable remains DTCG 2025.10, released Oct 28, 2025, per a secondary overview (CODERCOPS); the repo is at the Design Tokens Community Group. What’s new this week is tooling that uses tokens — notably the system checks that flagged token issues in Figma’s sample report.
5. Which of these features can I try today vs. waitlisted? The agent (GA since Oct 6), Make on Gemini 4 Argon (rolling out to all plans since Oct 13), Code Layers (open beta, all plans), Specs (open beta, paid), and Guidelines (open beta, paid) are in your hands today per the release notes and The Verge. Motion is open beta too. System Map is preview and Code Sources are closed beta (release notes). See the comparison table above.
How This Guide Was Built
This digest is desk research on official release notes and blog posts — Figma’s release notes, the build by design post, the Specs announcement, the Figma agent and design systems post, and The Verge’s coverage of agent GA — supplemented by the DTCG community group and one secondary digest item (Art Direction Daily, summarizing Archibald on JPEG XL vs AVIF). We did not run these tools hands-on. Statuses, dates, and plan tiers are reported as published on Oct 19, 2026, and anything we couldn’t confirm to a primary source is labeled above as single-source, secondary, or unverified.