On October 15, 2026, Figma launched Specs, a shared writing space on the canvas where teams record design decisions, product requirements and design language, plus written guidelines attached to design system libraries. Both are in open beta on paid plans, and Figma's agent and outside coding tools can read them. For tech companies, the practical takeaway is that brand and design rules now need to exist in writing, because AI tools will only follow what's written down.
What Figma launched
At Config India on October 15, Figma launched Specs, a place on the canvas where teams write down their decisions and design language so people and AI agents can work from the same source. A spec is a Markdown document, which is a fancy way of saying plain formatted text. You can drop designs, FigJam diagrams and prototypes right into it, and teammates and agents can comment in threads.
It came with a few related launches. Design system libraries can now carry written guidelines, which are instructions that tell Figma's agent how to use your components. Figma's agent is now generally available, and code layers, which put working, code-backed prototypes on the canvas, moved into open beta. Specs and guidelines are both in open beta on paid plans.
TechCrunch framed the whole release around one goal: helping Figma's agents, and outside agents, follow a brand's design rules. Figma's own wrap-up says agents can build on a team's craft when they're given "the right patterns and principles."
The catch: someone has to write the rules
That last part is where most tech companies are going to stall.
Plenty of teams have a component library. Far fewer have the reasoning written down. Why the primary button is used once per screen. When the illustration style shows up and when it doesn't. Which of the three card layouts is for marketing and which is for the product. What "on brand" means for an empty state or an error message.
Usually that knowledge lives in a senior designer's head, a few Slack threads and a brand PDF from the last refresh. People pick it up over time. An AI agent can't. Figma's guidance on its agent says this directly: clear component names, defined variants, complete examples and written guidelines are what keep it from falling back on generic styling.
So the new tools don't remove the need for creative direction. They make it visible. If your rules aren't written, the agent will produce something that looks fine and feels like nobody's brand in particular.
Why this matters past the design team
This isn't only a Figma story. Specs can be read through Figma's MCP server, the connection outside AI coding tools use, and Figma announced 20 new partner integrations with it. In practice that means the same written rules can follow your brand from the design file into the code your engineers, or their AI assistants, ship.
For a tech company, that's a real shift. Product marketing pages, in-app screens, sales decks and launch sites are increasingly built quickly, by more people, with AI help. The thing that keeps them looking like one company used to be a brand team reviewing everything. Now it's partly whatever context those tools can read.
What I'd write down first
You don't need a 60-page brand book. I'd start with a short spec covering:
- The one-sentence brand idea. What should every screen and page feel like? Write it so a stranger could use it to make a judgment call.
- Voice in practice. Three or four rules for how you write buttons, headlines and errors, with a "do this, not that" example for each.
- Color and type with a purpose. Not just the hex values, but when your accent color is allowed and when it isn't.
- Component choices. For any two components that look alike, a line on when to use which. Figma calls this out as a common source of agent mistakes.
- Two or three complete examples. A finished marketing page and a finished product screen that you'd happily show a customer. Figma's guidance leans heavily on examples, and people tend to learn from them faster than from rules too.
- What's off limits. Stock imagery styles, phrases or layouts you've retired. Exceptions are easier to follow when they're named.
Then treat it like a living document. Figma's advice is to fix recurring agent mistakes by updating the guidelines or examples, which is also good practice for human teams.
My take
The tools are getting good at producing design. They still can't decide what your brand should be. Specs is a smart format, but its value depends entirely on the quality of the thinking you put in it.
That's creative direction work, and it's the kind most fast-moving tech teams have postponed. Writing it down now pays off twice: new hires get up to speed faster, and the AI tools your team is already using start producing work that looks like it came from you.
Questions we hear a lot
What is Figma Specs?
Specs is a Markdown-based document that lives on the Figma canvas. Teams use it to record decisions, product requirements and design language, with designs, FigJam diagrams and code embedded alongside the text. Figma's agent and outside AI coding tools can read it as context. It went into open beta on all paid plans on October 15, 2026.
How does the Figma agent use a design system?
When a published library is connected, the agent builds with the team's approved components and variables instead of generic styling. Teams can attach written guidelines to the library covering rules, exceptions, common mistakes and how to choose between similar components. Figma says the agent is more consistent when creating new designs than when editing existing ones.
Do small tech teams need a design system to benefit?
Not a large one. Figma's own guidance stresses clear component names, defined variants, a few complete examples and written guidelines. A short, honest set of rules and examples gives an AI tool far more to work with than a big library with no explanation of how to use it.
Sources
- Figma Blog: Introducing Specs: Markdown as a medium (Oct 15, 2026)
- Figma Blog: Build by design: New workflows for new ways of building (Oct 15, 2026)
- Figma Blog: How to put your design system to work with the Figma agent (Oct 23, 2026)
- TechCrunch: Figma announces new features to define how agents work on its platform (Oct 14, 2026)
Filed under Tech Teams
Evan Walker
Founder & Creative Director at Satellite Black, with experience across a broad range of industries working as a Creative Director, Developer, and strategist.
