Loading

Encode the brand as a skill

Every Claude output across the org stays on-brand.

15 minDesignClaude Cowork
Loading

Set up

Connect your tools

Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access.

Add a connector for each tool you want Claude to use.

Figma
Read published variables, type styles, and components straight from the library file.
Connect
Notion
Pull the brand guidelines and voice doc from where the team already maintains them.
Connect
GitHubOptional
Read the design-tokens package so the skill stays in sync with what ships.
Connect

Set your working folder

Drag the files you'll use (the brand guidelines PDF, the voice and tone doc, the tokens JSON) into one folder on your machine, then give Claude access to it in the Claude desktop app. Claude reads from it and writes the skill definition back to it. If you maintain the brand system, create a project from that folder so updates to the guidelines flow through.

Brand / System-Source
brand-guidelines-2026.pdfFeb 3, 20263.4 MB
voice-and-tone.docxFeb 3, 202652 KB
tokens.jsonApr 20, 202618 KB
In Cowork’s chat bar:Brand / System-Source

The prompt

Copy this into Claude

Turn the brand docs in this folder into a shared skill called /on-brand. The skill should enforce our color tokens, typography, spacing, and voice rules on any content or UI it generates, and refuse off-brand patterns with a short reason.

Brand / System-Source

Why this works

Source

Point at your docs. The folder chip plus "in this folder" tells Claude your guidelines are the authority, not what it knows about branding in general.

Prompt

Name the output. Asking for "a shared skill called /on-brand" instead of "brand guidelines" is the difference between a reusable command and a one-time answer.

Prompt

List what it covers. "Color tokens, typography, spacing, and voice" — naming the parts means Claude reads those sections of your docs first instead of guessing what counts as brand.

Prompt

Define the failure case. "Refuse off-brand patterns with a short reason" is what makes the skill enforce rather than suggest, and the reason teaches whoever gets refused.

Get a better draft

Practice

Add an example to match. Drop an example you like into the folder and Claude matches your structure and voice.

Practice

Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.

Make Claude work for you

Your first /on-brand is a starting draft. Once Claude gives you a skill that passes your own brand review, tell Claude to harden it. Layer in your exception list, your sub-brand variations, your accessibility minimums, and the phrasing you never want to see. A few minutes of conversation and the skill enforces your system from then on.

Edit the /on-brand skill with my feedback.

Brand / System-Source

Make it repeatable

Share it as an artifact

Guidelines change; the skill should too. Ask Claude to publish a brand-compliance summary as an artifact so anyone can see exactly what /on-brand enforces today. Ask again when the skill changes and the summary shows the latest guidelines.

Publish a one-page summary of what /on-brand enforces as an artifact for the whole company.

Brand / System-Source

Re-sync it with every guideline change

The brand evolves; the skill should follow without a ticket. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and Claude drafts an update to /on-brand each week from the source folder and library.

Set up a scheduled task for Mondays at 9am: re-read Brand / System-Source and the Figma library and rebuild /on-brand, then give me a short changelog of what the skill now enforces differently.

Brand / System-Source
Scheduled taskActive
Brand skill re-sync

Each Monday at 9am, re-reads the guidelines folder and Figma library, drafts an update to /on-brand, and gives you a short changelog of what the update enforces differently.

Every Monday at 9:00 AMOpen in Claude

To use a folder on your computer during a scheduled task, keep your computer on and awake with the Claude desktop app open so Claude can access it.

Share with your teammates

Your /on-brand skill now carries your tokens, your type scale, your voice rules, and your refusal list. Share it workspace-wide so marketing, product, sales, and support all generate from the same system, and the design team stops being the brand police after the fact.

What changes for the design system team