Branding

Design System Governance

Governs a reusable design system: token and component ownership, versioning, accessibility contracts, adoption.

What it does

Governs a reusable design system: token and component ownership, versioning, accessibility contracts, adoption.

When to use it

Use for contribution rules, documentation, migrations, deprecation, or measuring real design consistency.

Problems it prevents

Stops a design system that exists on paper while half the product still ships one-off, undocumented components.

Typical workflow

  1. Establish scope and ownership
  2. Govern tokens and components
  3. Version and release deliberately
  4. Measure adoption honestly, including debt

Example output

A design system with a named owner per token category and a measured adoption rate, not just a Figma file nobody updates.

What's included

  1. 01
    The complete prompt

    The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

  2. 02
    Install walkthrough

    Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

  3. 03
    Use notes

    How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Installation

Save the manual as SKILL.md in ~/.claude/skills/design-system-governance/ to use it on every project, or in .claude/skills/design-system-governance/ to scope it to one repository. Then invoke it directly:

/design-system-governance

Read the official Claude Code skills guide

Works well with