Framer | Skills Keep Design and CMS Guidance Reusable
Framer introduced Skills on September 22, 2026, letting teams preserve instructions for recurring design, writing, and CMS work. For template creators, the feature can carry guidance about the intended design into the next person's editing workflow.
Project decisions can become reusable instructions
Skills can reference project pages, components, and styles through @pages, @components, and @styles. The /skills command asks the agent to create or update guidance, and Skills stay with a project when it is remixed.
A template might have a specific card hierarchy, a restrained spacing scale, and an editorial tone for page introductions. Capture the rules that define those choices, rather than preserving a long conversation with every experiment included. The next task needs the accepted direction.
Write guidance around concrete design behavior
A useful instruction tells the agent how to make a decision. Describe when to use an existing component, how headings relate, and which part of a page may vary. Avoid a vague request to keep everything beautiful or modern.
For CMS work, explain the field's purpose and the relationship between content and layout. If a summary needs to remain short enough for a card, describe that constraint with a representative example. Clear guidance helps a later editor understand the template as well as helping the agent.
Reuse should preserve the right level of control
A skill should support the project's design direction without freezing every page into the same composition. Distinguish shared rules from content-specific choices. A feature article and a contact page can use the same system while requiring different arrangements.
Review a new task on the canvas after the agent applies the guidance. Check whether it reused the intended components and whether the result remains appropriate for the content. Stored instructions are a useful reference, not evidence that every generated decision is correct.
Keep the instructions current and project-specific
When a design decision changes, revise the corresponding guidance so later work does not restore the old behavior. Keep unrelated project conventions out of the skill; they can make a correct request produce an unsuitable result.
For a template intended for remixing, include enough context for a new owner to understand its purpose. Explain the editing pattern in plain language and avoid references that only make sense to the original designer. Test it with a genuinely new page or content item.
REMEMBER: Review reusable instructions after a design change, and test them on a new task before relying on them across a template.{alertSuccess}
Daisuki's Take: What This Means for Web Designers
We see Skills as a way to make a template's design logic more portable. A new editor can receive guidance about the choices behind the layout, rather than only the layout itself.
We would preserve concise accepted rules and useful examples. The goal is to make the next task easier, not to turn the full history of a design discussion into instructions.
The practical benefit appears when a new page still feels like part of the same website. Review that result and adjust the guidance whenever it proves too vague, too restrictive, or out of date.
Sources and Recommended Links
- Skills | Framer Updates Official Site
