Published
9 MIN READ
Framer Skills: the manual the AI agent follows
Framer Skills are instructions saved in a website's project that Framer's AI agent follows when it works on that site: the design system, the brand voice, how to fill in the CMS and what to check before publishing. Launched on September 22, 2026, they turn spoken rules into written rules.
The announcement on the Framer blog, published on September 22 and updated two days later, presents skills as the way to teach the agent to work the way the team works. Portuguese-language tutorials on building websites in Framer have not caught up with them yet and stop at the prompt.
Wama uses Framer's agents heavily in its production workflow and has more than 50 projects published on the platform. That is where this guide's take comes from: the skill is the part of the website that keeps working after delivery, and whoever will run the agent needs it as much as the rules for using Agents in the company.
What are Framer Skills?
They are instructions with a name, a short description and a content field, stored inside the project. According to the official skills page, each one tells the agent how to do a specific task on that site: build a page with the design system, write in the brand voice, review SEO or check the launch.
The skill lives in the project, not in the account of whoever wrote it. Framer's updates log says it travels with the project when someone remixes it, and that it can reference the site's own pages, components and styles with @pages, @components and @styles. That is what sets it apart from a brand manual stored in a folder: the agent reads the rule and sees the piece it refers to.
There are two ways to create one. In Settings, under Skills, someone writes it by hand. In the chat, the /skills command asks the agent to write a new one or to capture the decisions from a conversation that reached a good result. Every conversation with the agent uses AI credits, part of the cost of a Framer project.
What is the difference between a skill and a prompt?
A prompt is for one task; a skill is for every task of that kind. The official page sums it up like this: the prompt asks the agent to finish a job, and the skill stores the instructions it should follow every time, without anyone having to rewrite them.
In practice, the difference shows up in the second week of use. Without a skill, each person on the team describes the website their own way when asking for a new page, and the agent interprets each request from scratch. With a skill, a short request is enough, because the rule is already in the project. The announcement adds that the command is not even required: the agent pulls in the skill on its own when its description matches the task.
That is why the description matters as much as the content: it decides when the rule comes into play. Write it like a good website brief, saying what the skill is for and which task to use it on.
Which skills does a company website need?
Four cover almost every corporate website: design system, brand voice, CMS content and launch check. The names follow the examples Framer itself publishes to copy and adapt, and each one answers a question the agent cannot answer just by looking at the canvas.
Skill | What it tells the agent | Who knows the answer |
|---|---|---|
design-system | Which components, text styles, colors, spacing and breakpoints to use on a new page | Whoever designed the website |
brand-voice | Brand terms, tone and what never to write | Marketing and whoever wrote the copy |
cms-content | Which collection fields to fill in and what cannot become loose text on the page | Whoever built the CMS |
seo-check and launch-check | Metadata, image alt text, links, forms and mobile screens before publishing | Whoever publishes the website |
The official list includes others, such as accessibility, effects and one that strips out the tics of AI-generated text. Start with the four in the table. The design system one prevents the most rework, because it stops the agent from inventing colors, fonts or components. The CMS one depends on what becomes editable content on the website, a decision made during the project, not after it.
How to write a skill the agent respects
Write verifiable rules and make the level of obligation clear. The Framer Academy best practices guide suggests three words: must for what the agent cannot change, prefer for the default path that allows exceptions and can for choices that do not affect consistency. Requests like making the page prettier do not belong.
Protect what already exists. Say what the agent can edit and what stays as it is: links, component instances, CMS-bound fields and interactions.
Point to examples from the site itself. With @, the skill references the page, component or style that serves as the model.
Write what the canvas does not show. Which component to use before creating another one, how the team names pages and layers, which breakpoints to review.
Define what done means. List the final checks and ask the agent to fix what it finds and report what it could not solve.
Test on two different tasks. When something goes wrong, rewrite the instruction that caused the error, without creating rules for problems that have not happened yet.
Item 3 is where the value lies. In Wama's projects, design is the longest phase, and it is where we decide how much breathing room a section needs or which call to action fits a launch page. Those decisions rarely stay visible in the final file. The skill is the place to write them down.
Who should write your website's skills?
Whoever designed the system, reviewed by whoever will run the website. The designer knows the rules; the company's team knows the tasks it will repeat. Written by only one side, the skill becomes a style manual nobody checks or a list of requests with no visual criteria.
At Wama, the project is transferred to the client's account at the end of the work, and the company becomes the owner of the website, the domain and the subscription. Since the skill lives in the project, it goes along. If you are hiring a website now, ask for the skills to be on the list of deliverables, next to the team's CMS training, and check what a studio delivers in a Framer project before signing.
Also ask who maintains the skills when the website changes. The healthy answer is the company itself, with occasional support from whoever designed it. To evaluate that support, see what to check in a Framer expert before choosing.
As a Framer Expert Pro, Wama has free editor access on client projects and a 50% discount on agent credits, benefits of Framer's Expert Pro tier. Post-delivery support does not depend on a monthly contract: there is a warranty period with free fixes and an open channel for one-off questions.
What the skill does not solve
The skill does not design the system, does not approve the result and does not isolate the change. It describes rules that need to exist beforehand; if the website has no organized styles and components, the skill only documents the mess. The announcement itself insists that each page still calls for design judgment and that review happens on the canvas.
Nor does it replace the process. Changes made by the agent still need a branch, a review and someone with permission to publish, topics covered in the guide on AI in the company website linked at the beginning of this text.
At Wama, AI sped up building, not deciding: the total timeline of our projects did not change, and the gain shows up in finish. Every AI output goes through human review before it reaches the client. A well-written skill shortens the path to the first acceptable version, but it does not take anyone out of the review.
Common mistakes when creating skills in Framer
One skill for everything. The official guide recommends splitting when triggers and outcomes change; each skill with one job and a clear finish line.
Adjectives instead of rules. Modern, clean and elegant do not tell the agent what to do.
Forgetting to protect content. Without that line, the agent may change text, links or CMS fields nobody asked to change.
A skill that is never reviewed. The website changes, and the old rule starts producing misaligned pages.
Treating the agent as free. The plan's AI credits run out; agree on who uses the agent and for what before opening it to the whole team.
Frequently asked questions about Framer Skills
Do Framer Skills cost anything?
The official sources we read do not list a separate price for skills. They live in the project settings and are used by the agent, and using the agent consumes the plan's AI credits. In practice, the cost is that of the work the agent does following the skill, not of the stored skill.
Do I need to know how to code to write a skill?
No. A skill is plain text, written in sentences and lists, and the agent can also draft the first version through the /skills command. What takes preparation is knowing the website's rules: which components to use, which fields to protect and what to check before publishing. That is design knowledge, not code.
Does a skill apply to all of the company's websites?
Not automatically. The skill stays tied to the project where it was created and goes with it when someone remixes it. A company with several websites needs to copy and adjust the skills in each project, which also avoids carrying over to one site a rule that only made sense on another.
Does a template with skills replace a custom website?
It helps, but it does not replace one. The official announcement anticipates templates that come with skills explaining how they were designed, which improves how the agent is used. The template, however, is still another brand's system. In a custom project, the system is born from the company's brand, and the skill describes rules that belong to it.
Who can create or edit the website's skills?
Anyone with edit access to the project opens Skills in the settings and changes the name, description and content whenever they want. The official sources we read do not detail restrictions by role. That is why it is worth agreeing inside the company who owns each skill, the same way you agree on who publishes the website.
If your company is going to hire a Framer website and wants the team to use the agent without breaking the system, talk to Wama about your project.
