Figma Skills Let You Bottle Your Design Judgment and Share It

Figma just made it easier to create and share agent Skills inside the app itself, and there is already a community library of them to pull from. If you have been using the Figma agent mostly for one-off prompts, this changes what the tool can actually do for you.

What a Skill Is, and Why It Is Not Just an Engineer Thing

A Skill is a plain-text markdown file, basically a small set of instructions, that tells the Figma agent how to behave in a specific situation. Think of it as a saved recipe: instead of explaining your preferences every single time, you drop in /your-skill-name and the agent already knows what you want.

The format sounds technical, but the underlying idea is pure design thinking. Every experienced designer carries around a set of opinions: which easing curves feel right, how tight the spacing should be, when animation helps versus distracts. Skills are just a way to write those opinions down so the agent can act on them consistently.

Until now, creating a Skill required editing a markdown file by hand. Starting today, you can ask the Figma agent to draft one for you, preview it, put it to work in your chat, and keep refining it. You can also open the markdown editor and edit directly if you prefer. The friction is gone.

The Real Thesis: Consistency at the Speed of a Prompt

The biggest promise here is not novelty effects or automation for its own sake. It is consistency. When designer Emil Kowalski at Linear built /find-animation-opportunities, he gave the agent his own instincts about motion: what should animate, what should not, and how to avoid over-animating. Anyone on his team can now invoke those instincts in a single slash command.

That is a meaningful shift for designers who are starting to build their own apps with AI tools. Right now, vibe-coded products often feel inconsistent because each prompt session starts from scratch. Skills let you carry your design standards forward from session to session, file to file, and even teammate to teammate.

10 Community Skills Worth Trying Right Now

Figma curated ten community Skills that show how wide the range of use cases already is. A few that stand out for product designers building with AI:

/better-interface by Jakub Krehel gives the agent a personal rulebook covering typography, layout, accessibility, motion, and product writing. It is designed to catch the small details that separate a good product from a great one. If you are iterating quickly with AI, this kind of checklist is exactly what stops corners from being cut without you noticing.

/find-animation-opportunities by Emil Kowalski scans a frame and identifies what should animate and what should stay still. It can even propose exact values, which you can apply yourself in Figma Motion or hand off to the agent. The creator suggests pointing it at one frame at a time and adding context about your target user for better results.

/camera-pan-and-zoom by Mallory Dean builds a nested layer setup (a camera rig) that mimics real camera movement, like a pan across a card grid or a zoom back to a full view. Useful if you are prototyping scroll-driven or cinematic moments without wanting to restructure your frames.

/make-a-type-scale is one the author built themselves: select some text, run the skill, and the agent builds a full type scale and generates matching font variables. For anyone who has manually fiddled with type ramp values, that is a genuine time save.

/image-audit checks every image in a file for exportability issues and drops a report directly onto the canvas. Simple, specific, and the kind of quality check that is easy to skip when you are moving fast.

How to Actually Get Started

The lowest-friction entry point is the Figma Community skills library. Browse it, find one that matches something you do repeatedly, and drop the slash command into your agent chat. You do not need to write a single line of markdown.

When you are ready to make your own, describe what you want to the agent in plain language: "Create a skill that checks my designs against our accessibility guidelines" or "Build a skill that applies our brand's motion principles to any frame I select." The agent drafts it, you preview and test, and then you refine. You can also start from a design frame as reference, which is a natural way to work if you already have a canonical example you want the agent to learn from.

Once a Skill works well, you can publish it to the Figma Community and let other designers build on it.

A Grounded Take on What This Does Not Solve Yet

Skills are only as good as the instructions inside them. If you write vague guidance, the agent will produce vague results. The quality of a Skill depends on how clearly you can articulate your own design principles, which is harder than it sounds for knowledge that lives mostly in your gut.

There is also the question of how Skills hold up as Figma's agent evolves. Markdown files authored today may behave differently as the underlying model changes. It is worth treating them as living documents rather than set-and-forget automations.

That said, the direction is right. Designers have always developed strong opinions through years of practice. Skills are a new way to make those opinions portable, shareable, and actually useful inside the tools where the work happens.