Individual skill
design-systems
Build, document, and maintain design systems with design tokens, component specifications, pattern libraries, naming conventions, and governance processes. Conduct system audits, define component hierarchies, and establish shared design languages.
skills/design-systems/SKILL.md
Source commit 7e25e66e87f64f9d3dea22198f9e29937e7c48f5
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 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)
- 123
- Repository last updated
- Sep 30, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- accessibility Repository topic
- claude Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- codex Repository topic
- cursor Repository topic
- design Repository topic
- design-critique Repository topic
- journeymap Repository topic
- ux-design Repository topic
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 13,345 bytesexamples/component-spec-walkthrough.mddoc · 11,786 bytesexamples/system-audit-walkthrough.mddoc · 7,201 bytesreferences/component-hierarchy.mddoc · 7,847 bytesreferences/design-tokens.mddoc · 9,431 bytesreferences/governance-and-maintenance.mddoc · 9,952 bytesreferences/pattern-documentation.mddoc · 8,884 bytesreferences/perceptual-patterns.mddoc · 11,164 bytestemplates/component-spec-template.mddoc · 4,203 bytestemplates/design-system-audit-template.mddoc · 5,300 bytestemplates/token-architecture-template.mddoc · 7,908 bytes
Read excerpt
# Design Systems
You are an expert in design systems — the interconnected patterns and shared practices that bring coherence to digital products at scale. Your recommendations are grounded in Brad Frost's Atomic Design methodology, Alla Kholmatova's pattern-driven approach, Nathan Curtis's system governance models, the W3C Design Tokens specification, and real-world systems including Material Design 3, Polaris (Shopify), Carbon (IBM), and Spectrum (Adobe).
*A design system is a product that serves other products. It is never "done." The measure of a good system is not its comprehensiveness on day one — it is whether it is still useful, still used, and still evolving a year later.*
---
## Core Concepts
### Two Types of Patterns
Every design system is built from two inseparable layers (Kholmatova):
