design-system-builder
Skill4 starsChanged 2 months agoMITView on GitHub
Construct a cohesive UI component library. Use when assembling reusable elements, setting up a UI kit, or auditing component consistency.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- yesith0106/Skillstheir own version, first seen Nov 1, 2026
- zebbern/claude-code-guidetheir own version, first seen Oct 30, 2026
- mattiazi/skillstheir own version, first seen Oct 20, 2026
- signerlabs/design-system-builder-skillstheir own version, first seen Oct 20, 2026
- thewyattbrocato/design-and-copy-skillstheir own version, first seen Oct 17, 2026
- Geruyang/skillstheir own version, first seen Oct 15, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- zebbern/claude-code-guide★ 4.7ksame name
- signerlabs/design-system-builder-skills★ 8same name
- Geruyang/skills★ 2same name
- gnegreiros-ux/agentica-design-system★ 2same name
- thewyattbrocato/design-and-copy-skills★ 2same name
- yesith0106/Skills★ 2same name
- mattiazi/skills★ 1same name
- novatic-cu/nova-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository46 other files it gives its agents.
- accessibility-reviewSkill
- accessibility-runtime-auditSkill
- adaptive-component-behaviorSkill
- ai-feature-ux-patternsSkill
- behavioral-pricing-psychologySkill
- business-model-readingSkill
- business-model-thinkingSkill
- cognitive-load-heatmap-predictionSkill
- component-style-guideSkill
- cross-functional-reviewSkill
- dark-mode-theming-systemSkill
- dashboard-layout-patternsSkill
- dashboard-scaffolding-contractSkill
- design-drift-detectorSkill
- design-to-code-handoffSkill
- design-tokensSkill
- error-boundary-resilience-designSkill
- flow-based-functional-testingSkill
- growth-impact-reviewSkill
- i18n-localization-strategySkill
- information-architectureSkill
- interactive-element-auditSkill
- kinematic-motion-choreographySkill
- micro-interaction-motion-designSkill
- module-registry-syncSkill
- mvp-scopingSkill
- perceived-performance-loadingSkill
- prd-traceability-matrixSkill
- product-discoverySkill
- product-strategySkill
- project-health-diagnosticsSkill
- qa-feedback-loop-orchestratorSkill
- responsive-breakpoint-strategySkill
- responsive-qa-auditSkill
- route-integrity-checkerSkill
- security-privacy-reviewSkill
- stakeholder-requirement-mappingSkill
- touch-gesture-interactionSkill
- typography-systemSkill
- usability-heuristics-checkSkill
- user-flow-mappingSkill
- user-research-synthesisSkill
- ux-chaos-monkeySkill
- visual-hierarchy-reviewSkill
- visual-responsive-regression-testingSkill
- visual-style-extractorSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Downstream: After defining each component, run it through component-style-guide to document all states.
- Distinctive: line 14
Ensure the foundation exists.
- Distinctive: line 20
Every component must account for its lifecycle: Default, Hover, Active, Disabled, Focus, Error.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design System Builder
A design system is a strict contract of composition, not a loose collection of parts.
Pipeline Integration
- Upstream: This skill requires
design-tokensandtypography-systemto be defined first — components are built ON tokens, not alongside them. - Downstream: After defining each component, run it through
component-style-guideto document all states. The design system is incomplete until every component has a full state matrix. Every interactive component must specify its motion behavior viamicro-interaction-motion-design. Reference motion tokens, not raw CSS transitions.
1. Token Audit
Ensure the foundation exists. Do not build components with hardcoded hex codes, raw pixel values, or arbitrary spacing. Use semantic tokens exclusively.
2. Base Components First
Build the primitives: Buttons, Inputs, Cards. Compose larger organisms only from these stable atoms.
3. Define States and Behaviors
Every component must account for its lifecycle: Default, Hover, Active, Disabled, Focus, Error. Specify motion token behaviors for transitions.
4. Audit Existing Libraries
- Inventory all instances of a component type in the product.
- Identify the core variants actually needed.
- Consolidate to the minimum set of flexible variants.
- Replace raw values with tokens.
Anti-Patterns
- Premature Abstraction: Building complex organisms before the atoms are stable.
- Token Avoidance: Hardcoding values "just for this one component."
- State Neglect: Forgetting to design focus and error states.
Completion Criteria
design-tokensandtypography-systemare defined and utilized.- Every base component exists and relies purely on tokens.
- The
component-style-guidecontains a full state matrix. - Interactive elements specify motion token behaviors.
Output Format
A component registry — code-based or design-tool-agnostic — accompanied by a Markdown inventory mapping every component to its token dependencies, state matrix, and motion behaviors. If a design tool is used (Figma, Penpot, Sketch, or any other), the component registry is the source of truth — the design tool is a communication layer, not the canonical source.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.