Figma | Skills Help the Agent Follow Design Team Workflows
Figma is showing how skills can make the Figma agent a more useful collaborator for design teams. Published on July 1, 2026, the article explains how reusable instructions can help teams package prompts, review processes, UX writing standards, design system knowledge, research context, and team rituals into repeatable workflows that the agent can invoke when needed.
Figma skills turn team knowledge into reusable agent workflows
Skills are designed to solve a common team problem: important workflow knowledge often lives in someone's head, in repeated prompts, or in scattered documentation. Figma describes a skill as a reusable set of plain-English instructions that teaches the Figma agent how to follow a specific process.
For web designers and template creators, this is useful because many design decisions depend on repeatable standards. A team may have rules for UX writing, accessibility checks, component usage, design critiques, brand voice, product naming, or how to prepare a file before handoff. Turning those rules into a skill can make the agent more consistent across projects.
Skills can help with critiques, writing, and user perspective
Figma highlights several ways teams can use skills to improve review work. A skill can simulate a stakeholder's feedback style, apply UX writing standards, or review an experience from the perspective of a first-time user.
That kind of workflow can be useful for landing pages, product pages, dashboards, onboarding screens, and template systems. Instead of asking the agent a vague question like whether a design is good, a team can invoke a skill that reviews the work through a specific lens, such as accessibility, clarity, brand consistency, or user friction.
Reusable rituals can make team workflows easier
Some skills are less about visual critique and more about team operations. Figma gives examples such as a catch-me-up skill that summarizes recent activity, a crit prep checklist that gathers project context, and a crit recap skill that organizes feedback into decisions, action items, and deferred items.
For web design teams, this can reduce the friction around meetings and reviews. A template project often includes comments, revisions, design decisions, frontend constraints, and content changes. A reusable skill can help capture that context so the team does not lose important decisions between design review and implementation.
Connectors can bring outside context into the agent
Figma also explains that skills become more useful when they work with connectors. With connectors, the Figma agent can bring in context from tools such as Slack, Notion, Asana, research libraries, project discussions, and other team systems.
This matters because design work rarely happens only inside the canvas. Product requirements, user research, stakeholder notes, feedback threads, and engineering constraints often live somewhere else. Skills can help the agent use that context while reviewing a design, preparing a critique, or turning feedback into tasks.
IMPORTANT: The Figma agent is available in open beta. Full seat users on Professional, Organization, and Enterprise plans can use it in Figma Design and Figma Make files, while View, Dev, and Collab seats can try it in drafts. The agent is free to use during beta.{alertWarning}
Skills can be created, published, and managed
Figma's help documentation explains that custom skills can be created manually or uploaded as Markdown files. Once installed, a skill can be invoked with a slash command, such as a design critique skill or a design system guideline skill.
Teams can also publish skills to a team or organization, update published skills, disable them, export them, or delete them. That makes skills more than one-off prompts. They can become reusable workflow assets that help a design team maintain shared standards across files and projects.
Daisuki's Take: What This Means for Web Designers
For web designers, Figma skills are useful because they make AI assistance less random. A generic agent response can help sometimes, but a skill that knows your design system, review process, accessibility checklist, or UX writing rules is much more likely to produce useful feedback.
We think the strongest use case is consistency. Template creators and frontend teams often repeat the same checks across pages: hierarchy, spacing, mobile behavior, contrast, empty states, component usage, and copy clarity. Skills can turn those checks into reusable workflows instead of relying on memory each time.
The practical takeaway is to start with simple skills. Build one for design critique, one for UX writing, or one for checking a page against your template standards. If the skill saves time and improves consistency, then it can be expanded or published for the rest of the team.
Sources and Recommended Links
- Got skills? Make the Figma agent a better collaborator | Figma Official Blog
- Custom skills for the Figma agent and Figma Make | Figma Official Help Center
- Work with the Figma agent in design files | Figma Official Help Center
