Claude for Designers: How a Design Studio Sets It Up

Claude for designers works best when you set it up the way a studio already runs: one Project per client with that client’s brand inside, a few Skills for how your team works, connectors for the tools that hold the live files, and Claude Code or Claude Design for the build. This guide covers each part as Anthropic documents it in November 2026, and how we wire a client’s brand into it at iframe design studio. Every client after the first reuses the same Skills and the same steps.

Claude for designers: the five parts a studio uses

Claude has grown from one chat box into several tools. These are the five a design studio touches, checked against Anthropic’s own docs.

Part	What it holds	Where it runs	Plans
Projects	A client’s files and instructions, with their own chat history	Claude apps	All plans. Free: up to 5 projects. Sharing: Team and Enterprise
Skills	A reusable task: a folder with a SKILL.md file and any files it needs	Claude apps and Claude Code	All plans, with code execution turned on
Connectors	Live access to outside tools through remote MCP	Claude apps, Claude Desktop, Claude Code	All plans. Free: one custom connector
Claude Code + CLAUDE.md	Project rules loaded at the start of every session	Terminal, IDE, desktop	Claude Code users
Claude Design	Prototypes, slides and one-pagers from your design system	claude.com/product/design	Research preview on Pro, Max, Team and Enterprise

A split that works: Projects hold the client. Skills hold the studio. Connectors hold the files that change. Keep those three apart and one client’s colors stay out of another client’s deck.

One Project per client

Anthropic describes Projects as “self-contained workspaces with their own chat histories and knowledge bases” in its help page on Projects. Each one has two parts: knowledge (files you upload) and instructions (text that shapes every reply in that Project). That maps neatly onto a client.

What goes into a client’s Project:

• The client’s DESIGN.md: colors with a job each, typography, logo files with links, and the brand rules.
• The Brand Link, so anyone on the team can open the current kit in a browser.
• The brief and any copy the client already approved.
• Instructions, four or five lines at most.

A starting instruction block:

You work on [Client] for our design studio.
Use only the colors, fonts and logo files in DESIGN.md. Never redraw the logo.
If a rule isn't in DESIGN.md, ask instead of guessing.
Write in US English. Keep product names exactly as the client writes them.

On Team and Enterprise plans you can share a Project with specific people as “Can view” or “Can edit”. Give edit rights to whoever owns the account, and view rights to everyone else, so the instructions change in one place. Free accounts stop at five Projects, so a studio with more than five active clients needs a paid seat.

The weak spot: project knowledge is a copy

Upload a ZIP of logos in March. The client tweaks the symbol in May. The Project still has the March files, and Claude will keep using them because nothing told it otherwise. That’s the ZIP file workflow again, now inside your AI tool.

We keep the files themselves on the client’s Brand Link and put a DESIGN.md in the Project that links to them. The links keep pointing at the current files. When colors or rules change, you replace one Markdown file instead of re-uploading a folder.

What that looks like for a real client

Monalia is a luxury suites client of ours. These are files from its kit:

Eight files for one logo, and that’s SVG only. Across Sinqlo, 537 uploaded logos produced 3,002 variations, about 5.6 per logo, and about 22 files per logo once SVG, PNG, PDF and WebP are exported. Upload all of those to a Project and Claude has to choose between near-identical files by their names.

A DESIGN.md turns that pile into a short list Claude can follow. Monalia’s logo files use five colors: #222222, #CFB400, #B6CCC2, #718472 and #FFFFFF. A first draft from the files alone reads:

## Colors
- Near-black #222222: logo, headings and body text
- Mustard #CFB400: brand background, one block per layout
- Pale sage #B6CCC2: soft section backgrounds
- Deep sage #718472: darker backgrounds, white logo on top
- White #FFFFFF: logo over photos and deep sage

## Logos
- Primary, stacked, black: light backgrounds
- Stacked on mustard: covers and social posts
- Stacked, white: over photos and deep sage
- Wordmark, black: narrow headers
- Symbol, black: favicons and avatars

The roles are our reading of the files. The client signs them off before they go into the Project. The fonts aren’t in the SVGs, since the type is outlined, so they come from the source files and never from a guess. For what a full file holds, see our walkthrough of Sinqlo’s DESIGN.md, and for which parts of a guidelines PDF are worth rewriting, brand guidelines for AI.

Claude Skills for designers: write down how your studio works

A Skill is a folder with a SKILL.md file: a name, a description, and instructions. According to the Claude Code skills docs, the description stays in context so Claude knows the skill exists, and the full body loads only when the skill is used. That makes Skills cheap to keep around.

In the Claude apps you upload a Skill as a ZIP from Customize, then Skills, then “Upload a skill”. Anthropic’s help center says Skills need code execution turned on. On Team and Enterprise plans you can share a Skill from its menu, and each person who receives it switches it on for themselves.

Keep brand facts out of Skills. A Skill is for a job your team repeats on every client: a brand check before handoff, sizing a post set, a copy review in your house voice. The brand comes from the Project or the repo, so one Skill works for all of them.

This is the brand check we’d hand any studio:

---
name: brand-check
description: Checks a layout, deck or page against the client's DESIGN.md before it goes to the client. Use when someone asks for a brand check or says a deliverable is ready.
---

1. Read the DESIGN.md in this project or folder.
2. List every color used. Flag any that isn't in DESIGN.md.
3. Check each logo is a linked file from the kit, not redrawn or recolored.
4. Check fonts against the typography section.
5. Report problems as a short list. Don't fix them unless asked.

It uses only name and description in the frontmatter on purpose. Outside Claude Code, uploads accept a short list of fields, and anything else makes the upload fail. With these two, the same folder works in Claude Code and in the Claude apps.

Connectors and MCP: give Claude the live files

Connectors let Claude reach outside tools. Custom connectors use remote MCP and are on every plan, with Free accounts limited to one. On Pro and Max you add one from Customize, then Connectors. On Team and Enterprise only an Owner adds it, under Organization settings, and each member then connects their own account. You can switch connectors on and off per chat from the “+” button.

We covered which servers a studio actually needs in the best MCP servers for designers: Figma for the design file, Playwright to check pages in a real browser, and one source for the client’s brand.

For the brand, Sinqlo MCP connects Claude Code, Cursor or Windsurf with one API key and one URL. Ask for a client by name and the agent gets live logo URLs, color values and font stacks. Every tool is read-only, so an agent can fetch a logo but can’t replace or delete it.

Claude Code for designers: one CLAUDE.md per client repo

If your studio builds sites or prototypes in code, Claude Code is where the brand has to be exact. Claude Code reads a CLAUDE.md at the start of every session, and that file can pull in other files with @path imports. So the client’s DESIGN.md goes in the repo root, and the CLAUDE.md points at it:

# Monalia website

See @DESIGN.md for colors, typography, logo files and brand rules.

- Use only the logo files linked in DESIGN.md. Never draw the logo in SVG or CSS.
- Colors come from DESIGN.md as CSS variables. No other HEX values.
- Run the brand-check skill before you call a page done.

Anthropic’s memory docs suggest keeping each CLAUDE.md under 200 lines, and note that imports don’t make a file cheaper to load. Short brand rules plus a linked DESIGN.md stay well under that. Put the brand-check folder in .claude/skills/ and commit it, and everyone on the repo gets it.

Claude Design: where the brand kit fits

Anthropic launched Claude Design on April 17, 2026, as an Anthropic Labs research preview for Pro, Max, Team and Enterprise. Enterprise organizations have it off until an admin turns it on. It makes designs, prototypes, slides and one-pagers from a prompt, uploaded images and documents, a codebase, or elements captured from a website. It exports to PDF, PPTX, standalone HTML and Canva, and it can package a finished design as a handoff bundle for Claude Code.

The part that matters to a studio: during onboarding, Claude Design builds a design system by reading your codebase and design files, later projects use those colors, typography and components, and a team can keep more than one design system. One design system per client fits the way studios work.

What it builds from is whatever you point it at. Point it at the client’s repo, with the DESIGN.md and linked logo files at the root, and the source is the real kit. Anthropic doesn’t describe DESIGN.md as a special input, so treat it as part of the codebase. Then check the output the way you’d check a junior’s first pass: every logo should be one of the kit’s files, never a lookalike drawn from the description.

Use it to explore directions and build decks fast. The final logo files, colors and fonts still come from the brand kit.

A per-client setup checklist

Step	Where	What goes in
1. Create the Project	Claude apps	DESIGN.md, Brand Link, brief, approved copy
2. Write the instructions	Project settings	4 or 5 lines: use only kit files, ask before guessing
3. Switch on studio Skills	Customize, then Skills	brand-check and your other repeat tasks
4. Connect the brand	Claude Code or another MCP client	Sinqlo MCP, or DESIGN.md in the repo
5. Add a CLAUDE.md	Client repo root	@DESIGN.md import plus build rules
6. Set up the design system	Claude Design onboarding	The client repo or design files

Steps 1 and 5 are where most of the time goes if you package the brand by hand. Manual export, renaming and packaging already takes 30 to 45 minutes per client project before any AI tool sees it. Every logo revision means doing it again and re-uploading to every Project.

With the kit on a Brand Link, step 1 is pasting one link and one file. You can open a live brand kit to see what sits behind that link. The kit also carries the logo set itself, every variation from horizontal to symbol (we covered the types of logos a full set includes), so Claude never has to work one out.

FAQ

What is the best way to set up Claude for a design studio?

One Project per client with that client’s DESIGN.md, Brand Link and short instructions. A few shared Skills for the tasks your team repeats on every client. Connectors or an MCP server for the files that change. Keep the client in the Project and the studio in the Skills.

Can Claude use my client’s brand colors and logos?

Yes, if you hand them over in a form it can act on. Colors and fonts work as text, with a job for each value. Logos need to be real files, linked or served through an MCP server. A logo described in words gets redrawn.

What is the difference between Claude Projects and Skills?

A Project is a workspace for one body of work, with its own files, instructions and chat history. A Skill is a reusable task in a folder with a SKILL.md file, and Claude loads it only when the task comes up, in any project.

Which Claude plan does a design studio need?

Projects, Skills and custom connectors are on every plan, with limits on Free: five projects and one custom connector. Sharing a Project with teammates needs Team or Enterprise. Claude Design is in research preview on Pro, Max, Team and Enterprise.

Give Claude each client’s brand once

Each client gets one Brand Link with every logo variation in SVG, PNG, PDF and WebP, the colors and fonts, and a DESIGN.md any agent can read, all built from the same kit. Drop the DESIGN.md into the client’s Project and Claude works from the same files the client opens. When the logo changes, the link serves the new one. See what a client receives or start free with up to 3 brand kits.