← Creative tools

Figma opens code layers and Specs betas for teams working with AI

The October 15 updates put interactive prototypes and shared written context on the canvas. Both are rolling out, with different access conditions.

View sources
In this article
  1. Prototypes join the canvas
  2. Specs gives the brief a shared home
  3. What to look for in a real handoff
  4. Sources & method
Cream, rust, and charcoal paper ribbons converging into an ordered stack.
AI Toolcast illustration · AI-generated

The practical takeaway

Try one small design handoff and check whether the implementation preserves the team’s decisions, including awkward edge cases.

Prototypes join the canvas

Figma moved code layers into open beta on October 15. The feature places working prototypes on the design canvas, where teammates can compare alternatives and ask the Figma agent to change interactions. Supported lightweight codebases can be imported from GitHub or a local folder.

Figma says teams can also extract editable design layers and push changed code to a branch for review. The announcement describes creating and editing within code layers as free on paid plans through November 4, 2026; the feature will use AI credits. That temporary offer should not be read as unlimited, permanent free use.

Source 1

Specs gives the brief a shared home

A second October 15 release, Specs, puts collaborative Markdown documents beside designs and diagrams. Figma says its agent can participate in comment threads, and coding agents can read a spec with linked context through Figma’s MCP server.

Specs is rolling out in open beta to paid plans across web, desktop, and mobile. A rollout announcement does not confirm that a particular account already has access.

Source 2

What to look for in a real handoff

Our analysis is that these additions could help a product manager, designer, and developer examine the same proposal. A working prototype can make an ambiguous requirement easier to discuss, while a written brief records why the team chose a particular behavior.

The test is whether those decisions survive implementation. Try a small flow with a success state, a failure state, and a recovery step. Ask a colleague to explain it using only the shared material, then compare the resulting implementation with the agreed behavior. That exposes missing context faster than judging how polished the first screen looks.

Both releases remain betas. We have not measured their reliability, compatibility with an existing project, or effect on a team’s delivery time. Treat the announced workflows as candidates for a contained trial.

Sources & method

Coverage of Figma’s October 15 product announcements with original analysis. We have not tested either beta; examples and capability descriptions come from Figma.

  1. Figma: Design together with code layers on the canvasPublished October 15, 2026
  2. Figma: Introducing Specs: Markdown as a mediumPublished October 15, 2026

Source pages reviewed October 16, 2026. Analysis and suggested evaluation methods are AI Toolcast’s own.

This article contains no sponsored placement or affiliate links.