design-system-creator

Generate design systems with CSS from tokens and component documentation.

181|30|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/erichowens/some_claude_skills --skill design-system-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-creator
Source: https://github.com/erichowens/some_claude_skills/tree/main/.claude/skills/design-system-creator
Command: npx skills add https://github.com/erichowens/some_claude_skills --skill design-system-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Builds comprehensive, scalable design systems and design bibles, including tokens, component documentation, and style guidelines. Enables consistent UI language, theming, and multi-brand support with robust documentation templates.

Core Features & Use Cases

  • Token architecture (primitive, semantic, component)
  • CSS architecture guidance (ITCSS, BEM)
  • Component documentation templates and usage guidelines
  • Style guide generation and theming for multi-brand systems
  • Cross-brand tokens for dark mode and accessibility
  • Anti-patterns and best practices to avoid token explosion and drift

Quick Start

Generate a complete design system skeleton with token architecture and a component documentation template for a new product.

Frequently Asked Questions about design-system-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a design system with tokens and CSS architecture?

Design systems built from tokens organize UI properties into three tiers—primitive, semantic, and component—then structure CSS using ITCSS methodology to generate production-ready stylesheets. This Skill provides token architecture templates, CSS organization guidance, and component documentation to establish a scalable, consistent foundation.

What's the best way to build a component library with design documentation?

Component libraries require standardized documentation templates, usage guidelines, and clear relationships to tokens. This Skill generates ready-made templates, style guides, and anti-pattern guidance to accelerate library creation and ensure consistent component behavior across teams.

How do I implement theming and dark mode across a design system?

Theming strategies use semantic tokens and CSS variables to swap color palettes and accessibility-compliant modes without duplicating component code. This Skill covers cross-brand token structures, dark-mode activation triggers, and multi-brand token support to enable flexible theme switching.

Can I use design tokens for multi-brand systems?

Yes. Multi-brand systems share a primitive token layer and diverge at the semantic and component levels, allowing brands to reuse CSS architecture while maintaining distinct visual identities. This Skill includes token-structure guidance and templates for scaling across multiple brands.

What are common design system anti-patterns I should avoid?

Token explosion, semantic-layer drift, and inconsistent naming conventions undermine scalability. This Skill provides anti-pattern documentation and best practices to prevent common pitfalls and maintain long-term system health.