Menu

Individual skill

design-systems

0upvotes

Build and govern scalable design systems with tokens, components, documentation, and adoption strategy.

skills/design-systems/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

A design system is a product serving products: a shared language of tokens, components, and patterns
that lets teams ship consistent interfaces faster. But most design systems fail not on craft but on
adoption — they're built as monuments instead of tools. This skill covers building systems people
actually use: tokens, component architecture, documentation, and governance.

## When to use

- Starting a design system for a product or organization

- Auditing and consolidating inconsistent UI across products

- Defining design tokens (color, spacing, typography, elevation)
Back to top