borghei/claude-skills/design-system-lead
Claude Code and agent skill by borghei/claude-skills
- community
Checking that the SKILL.md file is still in the repository.
Design systems leadership across component libraries, design tokens, and design-dev collaboration. Use when architecting a token system, building a component library, defining governance, or generating cross-platform tokens.
Install
npx vskill@latest install borghei/claude-skills/design-system-leadSKILL.md
The same SKILL.md was published earlier as borghei/claude-skills/design-system-lead.
Design System Lead
The agent operates as a senior design system lead, delivering scalable component libraries, token architectures, governance processes, and adoption strategies for cross-functional product teams.
Clarify First
Before generating the design system, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
- Brand color and any existing tokens: the primitive values to build from (drives the three-tier token architecture).
- Current maturity level: Emerging, Defined, Managed, or Optimized (decides whether you establish foundations or optimize governance).
- Target platforms: web (CSS/SCSS), iOS, Android (drives token export formats and Style Dictionary config).
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
Workflow
- Assess maturity - Evaluate current design system maturity (Emerging, Defined, Managed, or Optimized). Audit existing patterns, inconsistencies, and custom components. Checkpoint: maturity level is documented with evidence.
- Define token architecture - Build a three-tier token structure: primitive (raw values), semantic (purpose-based aliases), and component (scoped to specific UI elements). Checkpoint: every semantic token references a primitive; no hardcoded values remain.
- Build component library - Design and implement components starting with primitives (Button, Input, Icon), then composites (Card, Modal, Dropdown), then patterns (Forms, Navigation, Tables). Checkpoint: each component has variants, sizes, states, props table, and accessibility requirements.
- Document everything - Create usage guidelines, code examples, do/don't rules, and accessibility notes for every component. Checkpoint: documentation covers installation, basic usage, all variants, and at least one accessibility note.
- Establish governance - Define the RFC-to-release contribution process. Set versioning strategy (SemVer). Checkpoint: contribution process is published and reviewed by both design and engineering leads.
- Measure adoption - Track coverage (% of products using DS), consistency (token compliance rate), efficiency (time to build), and quality (a11y score, bug reports). Checkpoint: adoption dashboard is updated monthly.
Design System Maturity Model
| Level | Characteristics | Focus | |
|---|---|---|---|
| 1: Emerging | Ad-hoc styles, no standards | Establish foundations | |
| 2: Defined | Documented guidelines | Component library | |
| 3: Managed | Shared component library | Adoption, governance | |
| 4: Optimized | Automated, measured | Continuous improvement |
Token Architecture
Three-tier token system (primitive -> semantic -> component):
Example: Cross-Platform Token Generation
Component Library Structure
Component Specification: Button
Example: Button Implementation (React + CVA)
Governance: Contribution Process
Versioning Strategy
| Change Type | Version Bump | Examples | |
|---|---|---|---|
| Breaking | MAJOR | Component API change, token rename | |
| New feature | MINOR | New component, new variant, new token | |
| Bug fix | PATCH | Style fix, docs update, perf improvement |
Adoption Metrics Dashboard
Tool Reference
token_gen.py
Generates a three-tier design token system (primitive, semantic, component) from a brand color. Supports CSS, SCSS, and JSON output. Includes WCAG contrast ratio checking.
| Flag | Type | Default | Description | |
|---|---|---|---|---|
--color, -c | string | #0066CC | Brand color in hex | |
--format, -f | choice | summary | Output format: json, css, scss, summary | |
--tiers, -t | choice | all | Token tiers: all, primitive, semantic, component | |
--output, -o | string | (stdout) | Output directory for generated files | |
--json | flag | False | Shortcut for --format json |
component_scaffold.py
Generates component documentation scaffolds with props tables, variants, states, accessibility requirements, anatomy, usage guidelines, and code examples.
| Flag | Type | Default | Description | |
|---|---|---|---|---|
--name, -n | string | (required) | Component name in PascalCase | |
--category, -c | choice | (required) | Category: primitive, composite, pattern | |
--variants, -v | string | (category default) | Comma-separated variant names | |
--sizes, -s | string | sm,md,lg | Comma-separated size names | |
--json | flag | False | Output as JSON |
adoption_analyzer.py
Analyzes design system adoption across products by evaluating component coverage, token compliance, custom overrides, and accessibility scores. Produces a health dashboard with per-product and portfolio-level analysis.
| Flag | Type | Default | Description | |
|---|---|---|---|---|
input | positional | (required) | CSV file with adoption data or "sample" | |
--threshold, -t | int | 75 | Health score threshold for flagging | |
--json | flag | False | Output as JSON |
CSV columns: product, total_components, ds_components, total_tokens, ds_tokens, custom_overrides, a11y_score, last_audit
Troubleshooting
| Problem | Cause | Solution | |
|---|---|---|---|
| Token overrides in production | Teams bypassing design system | Run adoption_analyzer monthly; add lint rules for hardcoded values | |
| Inconsistent component behavior across products | Version drift | Enforce SemVer; automate DS dependency updates in CI | |
| Low adoption in older products | Migration cost perceived as too high | Prioritize high-traffic pages; create migration guides per product | |
| Token naming conflicts | No naming convention enforced | Adopt CTI (Category-Type-Item) naming; document in governance | |
| Component API breaking changes | Insufficient versioning discipline | Use codemods for migration; deprecation period of 2 minor versions | |
| Designers and developers out of sync | Figma/code token drift | Use Tokens Studio plugin; sync on every release | |
| Contribution bottleneck | RFC review queue backed up | Set SLA for reviews (48h); rotate reviewers weekly |
Success Criteria
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingproduct-team/design-system-lead/SKILL.md
Popularity
- Repository stars
- 1,121
- Repository forks
- 213
- 7-day trend score
- 34
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 19 May 2026, 6 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/borghei/claude-skills/design-system-lead)