How to Use Figma Agents Across Design Work

TL;DR

Figma agents use attachments, linked Figma files, connectors, reusable skills, and canvas context to produce designs that reflect real data and team conventions. Available in open beta in Figma Design, with beta access rolling out gradually for FigJam and Figma Slides, they can also analyze boards, generate diagrams, build presentations, and automate common cleanup tasks.

Transcript

Figma agents make your work faster, more efficient, and more fun. Now, they're available in open beta in design and coming soon to FigJam. >> And slides. >> Hi, I'm Rodrigo, product manager. >> I'm Sam, product designer. >> And I'm Luke, product manager as well. >> The configure updates to the Figma design agent enable you to leverage context and e... Read More

Key Insights

• Figma Design agents can use frames, libraries, mentioned assets, live URLs, attachments, connectors, and linked Figma files as context, giving teams several ways to ground generated work in existing designs, real information, and established resources.
• Attachments can include text files, spreadsheets, and images placed directly into the agent chat. A spreadsheet can supply real data for a new design, while other attached materials can provide requirements and reference content beyond what already appears on the canvas.
• Linked Figma files provide the agent with full design structure, including components, tokens, layout, and styles. This richer context allows the agent to reproduce existing visual patterns more accurately than it could from screenshots alone.
• Connectors use MCP to connect external tools with the agent, allowing live context to enter a design conversation and resulting context to pass back out. The demonstrated workflow uses customer research notes to inspire ideas, then links those ideas from a document.
• Agent threads preserve the story of the design process where collaborators can read it without holding a meeting. Teams may keep a chat private when working solo in a shared file, or share a particular chat directly through a link.
• Custom skills package workflows, conventions, preferences, and design practices into reusable plain-English instructions. Individuals and teams can call these skills on demand, such as applying a teammate's feedback practices to evaluate a design and place helpful annotations on the canvas.
• FigJam agents can generate and edit boards, incorporate documents or app data, analyze complex board content, assess bug priorities, create follow-up tasks, and produce architecture, sequence, database, and other technical diagrams for team alignment.
• Figma Slides agents can build a first draft from briefs and reference documents while following a team template. Users review and edit the proposed outline before generation, then can request broad changes, such as updating the color scheme throughout an inherited deck.

Questions & Answers

Q: How do Figma agents get context for design work?

Figma agents can receive context from a referenced design frame, a connected library, mentioned assets, or web search using a live URL. They also accept attached text files, spreadsheets, and images. Teams can paste links to Figma files or use MCP connectors to bring in live information from external tools, giving the agent material beyond the current canvas.

Q: How are attachments used with Figma Design agents?

Users can drop text files, spreadsheets, and images into the agent chat to provide additional context. The demonstration shows a spreadsheet being used to create a new design populated with real data. Attachments can therefore supplement the canvas with structured information, visual references, or written material that the agent can use while producing its output.

Q: Why should users link a Figma file instead of attaching screenshots?

A linked Figma file gives the agent access to the full design structure, including components, tokens, layouts, and styles. A screenshot does not provide that same underlying structure. By reading the original file, the agent can follow its patterns and create additional screens that more accurately match the appearance and construction of the existing designs.

Q: What do connectors let Figma agents do?

Connectors link external tools to Figma agents through MCP. They allow the agent to pull live context into a design conversation and pass context back to another tool afterward. One example brings Q3 customer research notes into the ideation process, then adds a section to the source document that links to the resulting design ideas.

Q: How do Figma agent threads support team collaboration?

Agent work occurs openly in threads that show the history of the design process. Anyone in the file can read a thread to understand how the work developed without requiring a meeting. When someone prefers to work alone inside a shared file, the chat can be made private, and individual chats can also be shared directly through links.

Q: What are custom skills in Figma agents?

Custom skills are reusable instructions that package workflows, conventions, preferences, and team expertise. They are written in plain English and can be shared so colleagues can invoke the same practices on demand. In the example, a teammate's feedback practices become a skill that evaluates a design and adds useful feedback as annotations directly on the canvas.

Q: What tasks can agents perform in FigJam?

FigJam agents can create and edit boards using prompts and external context from documents or apps. They can summarize complex boards, assess the priority of bugs, and create tasks for issues that require action. For technical work, they can also generate flowcharts and architecture, sequence, and database diagrams to clarify ideas, requirements, and implementation details.

Q: How do Figma Slides agents create and revise presentations?

Figma Slides agents can use briefs, reference documents, and a team template to propose a first draft presentation. Before generation, users see an outline that they can reorder, expand, or trim to shape the story. After generation, the agent can make deck-wide edits, such as changing the color scheme across an inherited presentation that does not follow the brand.

Summary & Key Takeaways

• Figma Design agents gain context from frames, libraries, assets, live URLs, attachments, connectors, and linked Figma files. File links expose components, tokens, layouts, and styles instead of only screenshots, helping agents reproduce established patterns. Suggested actions also make creating variations, renaming layers, and checking designs against a design system easier.

• Collaboration happens through visible agent threads that document the design process for everyone in a file. Chats can also remain private or be shared directly by link. Teams can write reusable skills in plain English to package workflows, conventions, feedback practices, and preferences, making shared design guidance available whenever colleagues need it.

• Upcoming FigJam agents can generate boards from external context, analyze complex boards, prioritize reported bugs, create tasks, and produce technical diagrams. Figma Slides agents can turn briefs and references into an editable outline, apply team templates, generate a polished first draft, and update elements such as color schemes across an entire deck.