Figma releases Agent to general availability with a 60% designer win rate

• Figma Agent is now generally available after beta, with Figma's launch post announcing improved latency, file search, library guidelines, and live views of teammates' agents.
• The updated Agent wins in ~60%+ of human-graded evals with professional designers, according to Figma's evaluation post, which also says it follows instructions better and handles longer tasks.
• Figma's context model now reaches beyond the current canvas: zoink's GA post says better context means shorter prompts, while the official release notes add file search, node paste, and Markdown guidance.
• Design-system adherence improved but remains below Figma's target; zoink's GA post says it is not where Figma wants it yet.

Library guidelines are Markdown files with rules, best practices, and anti-patterns that the agent reads when a selected library is enabled, according to the GA release notes. The Workflow Lab follows a temporary-access feature from stale component repair through compliance review to a component spec, while Figma's design-system guide turns the same idea into reusable audits and naming and token cleanup.

The new context surface includes improved latency, search across Figma files, and library-level guidelines, according to Figma's rollout post.

Figma's release notes list these new controls:

• Library rules: Upload Markdown files with rules, best practices, and anti-patterns. The agent reads them whenever the library is enabled.
• Cross-file context: Search for Figma files in chat, then reference design files, FigJam sticky notes, or Figma Slides content.
• Canvas context: Attach files with the prompt box or paste Figma nodes directly into a prompt.
• Team visibility: Watch or follow teammates' agents working live on the canvas.
• Creative tools: Generative plugins are generally available, and users can select an image model for on-canvas edits.
• Reusable workflows: Brainstorm, create, and publish custom skills, now available on the Starter plan.

Design-system documentation gets an always-on reader in LukeW's framing: LukeW's post says agents can read it every time they write code.

Figma reports a win in ~60%+ of human-graded evals with professional designers, and Figma's evaluation post attributes the result to better instruction following and longer-running task handling.

No sample size, task mix, or baseline appears in Figma's evaluation post. The number is a human-graded designer comparison, not a general benchmark score.

Better context means designers can prompt less extensively, zoink's GA post says, but design-system adherence is still short of Figma's goal.

Figma's design-system guide describes the work Agent can take on:

• Documentation: Draft component do's and don'ts, visual examples, variants, and API recommendations for handoff.
• Adherence audits: Inventory the components and tokens used on a screen, then map them to their libraries.
• Bulk repairs: Replace a component or token across a design, or swap in the current library version.
• Naming cleanup: Find inconsistent names such as hover, hovered, and mouse-over, then apply an agreed convention.
• Token checks: Inspect whether components use the right design tokens and annotate the values in use.

Guidelines are scoped to the selected library, and Figma's clarification says users must rerun the agent after adding or updating one.

Figma's Workflow Lab uses a fictional outdoor-meetup app to show where the agent fits around human design decisions.

1. Repair selected frames: The designer connects the current library and runs /repair-library-usage. Agent compares component instances and variable bindings, replaces clear deprecated matches, and annotates ambiguous cases instead of changing them.
2. Triage critique: Agent reads comment threads, groups recurring feedback, surfaces contradictions, and separates actionable changes from open questions.
3. Review compliance: The /compliance-review skill references the security and compliance team's external checks, then annotates the frames where policy questions apply.
4. Draft the system change: When the flow exposes a missing expiration state in the shared item row component, /document-component-enhancement drafts a spec in the same Figma file instead of creating a detached custom component.

One designer said Agent had augmented her workflow in “delightful and surprising” ways, according to amylimabean's post.

She later called it a constant companion and said she uses skills to operationalize her workflow amylimabean's follow-up.

The team signaled more iteration in a short reply, with zoink's reply saying it was “always cooking.”

Access varies by plan and seat. Figma's design-system guide says full-seat users on Professional, Organization, Enterprise, and some Education plans get access; Starter is limited, while Collab, Dev, and View seats can use the agent in drafts.

The release notes say Agent began using AI credits on October 6, the day it became generally available.