Markdown edition

# Build and check a reusable Claude Design system

> Create a reusable Claude Design system from approved brand assets, review its rules, test a new design and verify who can use it.

By BIG CHANGE Editorial

Published: 2026-10-20T15:24:38.202Z
Updated: 2026-10-20T15:24:38.202Z
Canonical: https://bigchange.ai/blog/claude-design-reviewed-brand-system-guide

![Conceptual charcoal illustration of a wide unbranded layout proof emerging from a print press, with three plain samples clipped to its side rail.](https://bigchange.ai/api/media/file/claude-design-brand-system-proof-hero-v1.png)
AI-generated conceptual illustration by BIG CHANGE.

Claude Design can turn approved brand material into a system that new designs and decks can use. The useful result is more than a palette: it is a saved, reviewed set of colors, typography, components and layout rules whose use you can check in a new design. This guide is for the brand owner or designer authorized to handle the source files and approve the result. It is a documented workflow; BIG CHANGE has not created or tested a system in a Claude account.

## The big change

- **What changed:** Claude’s current chat and Artifacts route lets an authorized owner create reusable design rules from approved brand references. The generated system still needs review before team use.
- **Why it matters:** Comparing and correcting its rules, then testing a new design, gives the owner a way to check whether the saved system carries the intended brand into actual work.
- **What to watch:** The owner still needs to verify inheritance in that design, asset and font rights, accessibility checks and the final sharing audience. An attractive first output does not settle those questions.

## Prepare the sources and the account

Design systems are in beta on Pro, Max, Team and Enterprise plans. Basic Claude Design is available more broadly, but that does not give every account the design-system feature. Check the intended organization and account. On Enterprise, an owner may need to enable Design systems under Organization settings > Artifacts; organization settings and custom roles can also limit access. If your organization has storage or data residency requirements, resolve them before submitting files: Anthropic says Claude Design currently does not support data residency requirements and that uploaded assets are stored persistently.

Collect at least one approved source, such as a current brand guide, a permitted logo and font set, a representative deck, or an owned component library. For each, note the owner, revision, usage and processing rights, and any known conflict. Ask the brand owner to resolve conflicting color values, font licenses or logo rules. A missing decision stays open; Claude cannot approve a brand value on the owner’s behalf. Choose a representative design your team actually needs, and decide who may review and who may later receive the system.

Keep a private working record with the source versions and rights, the account and organization, the system’s name and owner, and the revision you reviewed. Leave spaces for color roles and values, type families and licenses, logo variants and usage rules, component variants and states, spacing and layout rules, independent accessibility results, test-design identity, approval and sharing readback. These are your review records, not fields promised by Claude.

## Build and review the system

1. **Open Design systems in the intended account.** Confirm that the feature is available and that you are in the right organization. Anthropic’s current route lets you ask Claude in a chat to build a system from connected or uploaded brand material, then manage systems under Settings > Design systems. If access is missing, record the actual plan, feature or role barrier before continuing. Do not move sensitive assets to a personal account to get around it.
2. **Give Claude the approved references and a bounded request.** Upload or connect only the material you are allowed to process. A plain-language request is enough: “Create a design system from these approved references. Identify the source for each proposed color, type rule, logo instruction, component and layout pattern. Flag missing or conflicting rules for owner review instead of inventing them.” Record the actual input revisions and the identity of the system Claude creates. If a real design system already exists as React components, Anthropic documents `/design-sync` in Claude Code as another route; use it only with authorized code and access.
3. **Audit the generated system against the sources.** In its artifact, inspect every material color role and value; type family, weight, scale and font license; logo variant, clear space and prohibited use; component, variant and state; spacing, grid and layout pattern. Check that its usage notes explain when each rule applies. Mark unsupported or missing items as unresolved, and get the owner’s decision before changing them. A generated logo concept does not become a licensed brand mark because it looks plausible.
4. **Correct, document and save a reviewed revision.** Ask Claude to change only the rules for which you have an approved source or explicit owner decision. Reopen the saved system and compare the corrected values with the references. Keep your own dated change record and a permitted copy of the guidance: Anthropic says Claude Design does not yet have version history. Record the system identity, owner, source revisions, reviewer and unresolved items with the revision you intend to test.
5. **Run checks outside the system artifact.** Measure the intended text and background pairs, including component states, with an independent contrast checker against your project’s applicable standard. WCAG 2.2’s minimum text criterion is 4.5:1 for ordinary text and 3:1 for large text, subject to its stated exceptions. Check font rights and legibility, responsive layouts, focus visibility and keyboard behavior in the actual design where those checks are available. Anthropic says live component previews inside a design-system artifact cannot be reached and operated with Tab; reading their names and notes is not a keyboard test. Record any check you could not perform as unresolved. A contrast pass alone does not prove overall accessibility.
6. **Test inheritance in new work.** Start a fresh representative design from a chat or the Artifacts Design template with the reviewed system attached or selected. Inspect the actual canvas at relevant sizes and compare its color roles, type, logo use, components, states and spacing with your saved revision. If a rule drifts, correct the system or the design as appropriate, then create or refresh the test and inspect it again. Reopen both the saved system and the test design in the intended account. One successful test shows what happened in that design; it does not guarantee every later output.
7. **Share only after the owner’s decision.** Designs start private. If the outcome is a private reviewed system, leave it private and record that state. If team use is approved, use the current Artifacts sharing controls and read back the audience. Anyone with Design systems access can create one and share it with specific people; an organization Owner or Primary Owner must share it with everyone or set the organization default. A system must be shared with everyone before it can become that default. To share another creator’s system organization-wide, the Owner or Primary Owner first needs the creator’s invitation at the highest access level. Confirm the final owner, audience and default in the right account. The standalone claude.ai/design app has separate publication controls and is scheduled to close on December 14, 2026; its Published toggle is not the Artifacts sharing step.

## When the result does not check out

If the feature is unavailable, verify the plan, Artifacts setting and role, then stop at the specific access boundary. For a failed upload or connection, inspect the response and the permitted source before a bounded retry. If the sources disagree, return the decision to the brand owner; do not fill the gap with a generated value. If a saved rule or new design differs from the approved reference, correct it and repeat the comparison. If a sharing change has an uncertain outcome, read back the current audience and default before trying again. A later brand revision calls for another review of affected rules and test designs.

Claude Design work draws from the same usage pool as the rest of Claude, including Claude Code; extra usage credits may be available when enabled. Large inputs and repeated iterations can use more of that allowance. This guide did not measure time, cost or output quality. Anthropic documents design exports such as a ZIP, PDF, PowerPoint or standalone HTML, but that does not establish an automatic design-system CSS, JSON, Tailwind or Figma-token export. Verify any required downstream format in the actual current product before promising a handoff.

You are done when the saved system has an identified owner and reviewed revision; material colors, fonts, logos, components and instructions trace to approved sources; independent checks are recorded with unresolved items visible; a new design visibly uses the reviewed system; and the intended audience and default state have been read back. For a different route to an owner-approved design specification for Claude Code, see our [DESIGN.md guide](https://bigchange.ai/blog/claude-code-owner-approved-design-md-guide).

## Sources & further reading

- [Anthropic: Set up your design system in Claude Design](https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design) — plan eligibility, chat and React-component creation routes, saved-system management, source material, test-project advice and the keyboard limitation. Its later standalone-app instructions are a separate route.
- [Anthropic: Artifacts admin guide for Team and Enterprise plans](https://support.claude.com/en/articles/16994751-artifacts-admin-guide-for-team-and-enterprise-plans) — current organization controls, sharing and default permissions, usage, persistent uploads and the data-residency limitation.
- [Anthropic: Get started with Claude Design](https://support.claude.com/en/articles/14604416-get-started-with-claude-design) — current chat and Artifacts creation, system attachment, canvas review, privacy, shared usage and lack of version history.
- [Anthropic: What are artifacts and how do I use them?](https://support.claude.com/en/articles/17153992-what-are-artifacts-and-how-do-i-use-them) — template-based design export options; it does not promise design-token interoperability.
- [W3C: Understanding WCAG 2.2 Contrast (Minimum)](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html) — text contrast thresholds and exceptions for an independent check.

## Sources

- [Set up your design system in Claude Design](https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design) — Paid-plan beta, approved input types, chat creation, React /design-sync alternative, system management, test-project guidance, keyboard limitation and separate standalone instructions.
- [Artifacts admin guide for Team and Enterprise plans](https://support.claude.com/en/articles/16994751-artifacts-admin-guide-for-team-and-enterprise-plans) — Artifacts settings and roles, organization-wide sharing/default sequence, creator invitation, shared usage, persistent uploads and data residency limit.
- [Get started with Claude Design](https://support.claude.com/en/articles/14604416-get-started-with-claude-design) — Current chat and Artifacts routes, design-system inheritance, private designs, usage pool and version-history limitation.
- [What are artifacts and how do I use them?](https://support.claude.com/en/articles/17153992-what-are-artifacts-and-how-do-i-use-them) — Design export options; does not establish automatic design-system token exports.
- [Understanding WCAG 2.2 Contrast (Minimum)](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html) — Text contrast minimum thresholds and exceptions; independent measurement remains the reader's task.
- [Create an owner-approved DESIGN.md for Claude Code](https://bigchange.ai/blog/claude-code-owner-approved-design-md-guide) — Contextual related BIG CHANGE guide #433, not a dated follow-up.