From prompts to team practice
Figma has expanded its design agent with skills: reusable markdown instructions that can be created, tested and shared from within a design workflow. The important idea is not that designers can save a long prompt. A skill can capture the small standards a team repeatedly applies—how to document a component, check interface states, audit colour tokens or prepare a usability test.
How authoring works
A designer can ask the agent to create a skill from a reference frame or a set of guidelines, preview the draft and revise it through chat or a markdown editor. Skills can then be invoked with a slash command. Figma also lets creators publish them to a Community library, and says many can work through its MCP server with external agents.
The most useful examples are unglamorous
Figma’s examples focus on work that is easy to skip under deadline pressure: checking missing loading and error states, documenting component variants, finding hard-coded colours, identifying motion opportunities and building discussion guides for usability tests. These tasks rarely produce a dramatic demo, but they improve handoff quality and consistency. Packaging them as repeatable instructions may help teams apply the same review more often.
A skill is not a design system
Written instructions cannot replace maintained components, variables or professional judgment. A skill may encode outdated rules, apply advice too broadly or make confident changes without understanding the product context. Teams will need owners, versions and review processes, particularly when a skill edits many objects automatically. Community popularity is also not proof that a workflow is accessible or appropriate.
The broader design shift
Design tools are moving from generating isolated screens toward automating the discipline around them. That makes the source of the instructions increasingly important. Figma skills could give experienced designers a way to make their reasoning reusable instead of leaving it in review comments or personal habit. Their real value will be measured by fewer missed states and cleaner handoffs, not by how many commands a Community page collects.
A sensible team rollout would begin with one low-risk skill, such as a documentation checklist, and compare its output with an experienced designer’s review. Record which suggestions are consistently helpful, which require correction and who approves updates to the instructions. That process turns a clever automation into maintained team knowledge. It also makes failures visible before a skill is allowed to rename components, alter tokens or apply changes across an entire product file.
