Framer published a changelog entry on September 22, 2026 introducing Skills: a way to save instructions that its AI agent reuses across tasks, instead of you re-explaining the same conventions in every prompt.

What changed

Until now, getting consistent output from Framer’s agent meant repeating context in each request. “Use our brand colors.” “Match the tone of the rest of the site.” “These CMS fields work this way.” Skills lets you save that context once, as reusable instructions covering things like a design system, a writing style, or a CMS workflow, and reference it across tasks going forward. The feature also supports referencing specific project elements, pages, components, and styles, by name inside a Skill, so the agent can be pointed at “the primary button component” or “the pricing page’s layout” instead of having that described from scratch every time. Framer’s changelog is clear that control stays with the person driving the agent: it follows the saved instructions, but you keep control of the result on the canvas.

Why it matters for designers

This targets a specific friction point in agent-assisted design work: an agent that’s generically capable but doesn’t know your specific conventions produces output that’s technically fine and practically unusable, off-brand colors, a CMS structure that doesn’t match your existing content model, copy in the wrong voice. Saving that context once, instead of re-typing it into every prompt, is the difference between an agent you have to correct every time and one that starts closer to right.

If you’re maintaining a consistent design system across a large site, or running the same conventions across multiple client projects at an agency, this is also a way to write down institutional knowledge somewhere more durable than a Slack thread or one designer’s memory, as long as the Skills themselves get kept up to date as the system evolves.

What to watch out for

We haven’t tested Skills hands-on yet, so treat the “before you use it” panel in the sidebar as open questions. Worth checking directly before relying on it for client work: whether a Skill is scoped to one project or shared workspace-wide (relevant if you work across multiple clients in one Framer workspace), and whether it’s practical to keep a saved Skill in sync as your actual design system changes. We’ll follow up with a Test once we’ve put it through a real project.