Claude Code replacing Figma is already visible in some prototype workflows, but Figma's November 2026 answer is to make code, agents, GitHub repositories and AI media generation part of Figma. The change is not that Figma declared design tools obsolete. The change is that Figma is trying to absorb the workflows that made separate AI coding tools attractive to product designers.
Figma Blog published a Workflow Lab post on November 4, 2026, showing code layers and the Figma agent as a way to build, compare and edit interactive prototypes on the Figma canvas. On November 6, 2026, Figma Blog published an excerpt from Dylan Field's All-In interview with David Friedberg, where Field argued that AI lowers production barriers but does not replace a designer's point of view. The practitioner signal arrived one day later, on November 7, when a product designer posting in r/ClaudeCode said their team at HubSpot had not opened Figma that week and had instead used Claude, Claude Code, GitHub branches and Loom around a shared prototype.
Is Claude Code replacing Figma
Claude Code is replacing Figma for some code-first prototype work, but the evidence does not show a broad migration away from Figma. The r/ClaudeCode post describes one team workflow, not market adoption data, and the poster explicitly wrote, "I don't think Figma is dead." Two top comments also cut against a clean replacement story, with one saying, "I use Claude *and* Figma."
For product teams, the practical change is that high-fidelity prototype work can now start in an AI coding environment and move through GitHub branches before it touches a traditional design file. That does not prove Figma is being abandoned. It proves the prototype has become the shared artifact, and Figma has to compete for that artifact.
The HubSpot designer's described workflow matters because it names the handoff mechanics. The team brainstormed in Claude with shared context, used Claude Code to build several working directions, consolidated the chosen direction into one GitHub repository, and then had each designer refine work in separate branches before merging. That workflow attacks one of Figma's historic advantages, live multiplayer collaboration, by moving collaboration into branches, merge conflict resolution, Loom updates and live links.
How Figma pulls code onto canvas
Figma pulls code onto the canvas by turning existing code, generated code or imported code into a code layer that designers can inspect, duplicate, prompt and edit visually. In the November 4 Workflow Lab, Figma Blog describes a designer cloning a connected GitHub repository from the Figma agent panel, keeping the main branch selected, and loading the app's existing map screen into a code layer.
Once the code layer is on the canvas, the Figma agent can generate multiple interactive alternatives side by side. In Figma's example, the designer asks for three versions of a delivery button: an omnisearch address field, a map-based selection and address shortcuts. Teammates can click through the versions, leave comments on the canvas, create their own variations and combine parts of different directions into one prototype without moving between separate links in separate tools.
| Figma capability | What it does | Why it matters |
|---|---|---|
| Code layers | Places interactive code-based prototypes on the Figma canvas. | Designers can compare working options beside design frames and comments. |
| Figma agent | Builds or edits code layers from prompts, frames, repositories, folders or connected sources. | Teams can generate several product directions without leaving the shared canvas. |
| GitHub repository cloning | Loads a connected repository and branch into a code layer. | Existing product code becomes the starting material for design exploration. |
| Extract designs | Turns a screen, element or recorded flow into editable Figma design layers. | Designers can move from working code back into visual design controls. |
The mechanism explains the effect. Claude Code and similar tools are attractive because they produce working prototypes directly. Figma's code layers try to preserve that benefit while adding the multiplayer canvas, side-by-side comparison, comments and visual editing that design teams already use. The Figma Blog post also says teams can create a code layer with the Chrome extension, an existing design frame, an empty prompt, an uploaded folder, a connected GitHub repository or an external coding agent through MCP.
Where the evidence is thin
The evidence is thin on adoption, retention and whether designers are actually reducing Figma usage at scale. The Reddit post is useful practitioner signal because it gives a concrete workflow, but it is one post in r/ClaudeCode with 14 comments and cannot support claims about the wider design market. Figma's own posts show product direction, not independent usage data.
The strongest supported claim is narrow: some product designers can now run collaborative prototype work through Claude Code and GitHub, while Figma is adding code layers, the Figma agent and Weave to keep that work inside its platform. Claims about Figma being dead or Claude winning design are not supported by the evidence here.
The sources also differ in what they emphasize. Figma Blog's November 6 excerpt frames Field's comments around human creativity, design and AI as production gets cheaper. The original All-In with Chamath, Jason, Sacks and Friedberg episode page, published through Wave, frames the interview as "Dylan Field: Is AI Replacing Designers?, Design is the New Code & Democratizing Creativity" and places the AI discussion around 21:53 to 40:16. The All-In material also includes a point omitted from the Figma excerpt: Field said Figma internally asks people using AI in writing to put written with AI at the top so readers can assess trust and care.
What teams should check now
Teams should audit where prototypes now live, then decide which artifact is the source of truth: a Figma file, a GitHub branch, a Claude Code project or a live prototype. The specific risk is version drift. If a designer edits a code layer in Figma while another designer refines a branch in GitHub, the team needs a clear merge path and a rule for which change wins.
For Figma users, the immediate checks are concrete. Test whether the team's connected GitHub account can clone the right repository and branch into a code layer. Open the code editor from a code layer and inspect Files before treating the agent's output as production-adjacent. Use Extract designs on a screen or element to see what survives as editable Figma layers. If the team uses Notion for PRDs, test the Notion connector path that Figma describes for giving the Figma agent requirements before it builds a code layer.
For teams already using Claude Code, the check is governance rather than tool access. The r/ClaudeCode workflow used branches, merges, conflict resolution, Looms and live links. That means design review has moved closer to software review. Product design leaders should decide whether prototype branches require naming conventions, reviewer assignment, merge approval and a visible link back to the product requirement or design brief.
What marketers should infer carefully
Marketers should infer that Figma wants AI-generated campaign and media work to connect back to design systems, but the evidence does not show any direct effect on Google rankings, Google Ads auctions or AI answer citations. The connection is operational. If creative teams produce more ad variants, product imagery and landing-page concepts with AI workflows, search and paid media teams need stronger controls over consistency, claims and measurement.
Figma's October 31, 2026 Weave explainer says Figma Weave brings AI generation and editing tools into connected, reusable workflows. Figma defines a node as a workflow building block, a workflow as connected nodes that turn starting material into a finished result, a branch as a separate exploratory path and a Weave tool as a packaged workflow someone can run without editing the underlying nodes. The same post says Weave can be used for product imagery, campaign visuals across channels and markets, and video work from reference images or existing clips.
That matters for search visibility and AI citations because campaign assets and landing-page changes already affect what gets crawled, indexed, measured and quoted. This is an inference from the workflow evidence, not a claim Figma makes. If Weave makes it easier to produce localized campaign visuals or product imagery, marketing operations teams should keep source frames, final assets, ad destinations and analytics naming tied together so the generated work does not outrun approvals and tracking.
Figma's Help Center says Figma announced the acquisition of Weavy in October 2025, and that Weavy is being reintroduced as Figma Weave. The FAQ describes Figma Weave as a creative platform for AI-native media generation and editing, available as a standalone experience, with integration into the rest of the Figma platform planned over time. The next trigger to watch is that integration stage, because it will show whether Figma can keep code prototypes, design layers and AI media workflows in one operating model instead of watching them split across Claude Code, GitHub and standalone generation tools.