design-system-creation
Complete workflow for creating distinctive design systems from scratch. Orchestrates aesthetic documentation, token architecture, components, and motion. Use when starting a new design system or refactoring an existing one. Triggers on create design system, design tokens, design system setup, visual identity, theming.
Best use case
design-system-creation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Complete workflow for creating distinctive design systems from scratch. Orchestrates aesthetic documentation, token architecture, components, and motion. Use when starting a new design system or refactoring an existing one. Triggers on create design system, design tokens, design system setup, visual identity, theming.
Teams using design-system-creation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/design-system-creation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How design-system-creation Compares
| Feature / Agent | design-system-creation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Complete workflow for creating distinctive design systems from scratch. Orchestrates aesthetic documentation, token architecture, components, and motion. Use when starting a new design system or refactoring an existing one. Triggers on create design system, design tokens, design system setup, visual identity, theming.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Design System Creation (Meta-Skill)
Complete workflow for creating distinctive design systems with personality.
## Installation
### OpenClaw / Moltbot / Clawbot
```bash
npx clawhub@latest install design-system-creation
```
---
## When to Use
- Starting a new product that needs visual identity
- Refactoring an existing design with scattered styles
- Building a component library with design tokens
- Want to go beyond generic Tailwind/Bootstrap aesthetics
---
## Workflow Overview
```
1. Aesthetic Foundation → Document the vibe before code
2. Color Token System → CSS variables + Tailwind + TypeScript
3. Typography System → Font stack + scale + patterns
4. Surface Components → Layered primitives with CVA
5. Motion Tokens → Consistent animation timing
6. Loading States → Skeleton + shimmer patterns
```
---
## Step 1: Aesthetic Foundation
**Read:** `ai/skills/design-systems/distinctive-design-systems`
Before writing CSS, document the aesthetic:
```markdown
## The Vibe
[1-2 sentences describing the visual feel]
## Inspirations
- [Reference 1 - what to take from it]
- [Reference 2 - what to take from it]
## Emotions to Evoke
| Emotion | How It's Achieved |
|---------|-------------------|
| [X] | [specific technique] |
| [Y] | [specific technique] |
```
### Proven Directions to Consider
| Aesthetic | Characteristics |
|-----------|----------------|
| Retro-futuristic | CRT textures, glow effects, monospace fonts |
| Warm cyberpunk | Tan/beige base, emerald accents, glass panels |
| Magazine financial | Bold typography, dark theme, gradient text |
---
## Step 2: Color Token Architecture
**Read:** `ai/skills/design-systems/distinctive-design-systems`
Create the three-layer token system:
```css
/* 1. CSS Variables (source of truth) */
:root {
--tone-primary: 76, 204, 255;
--primary: 200 90% 65%;
--success: 154 80% 60%;
--destructive: 346 80% 62%;
}
```
```typescript
// 2. Tailwind Config
colors: {
primary: 'hsl(var(--primary))',
tone: { primary: 'rgb(var(--tone-primary))' },
}
```
```typescript
// 3. TypeScript Tokens (optional)
export const colors = {
primary: 'hsl(var(--primary))',
};
```
---
## Step 3: Typography System
**Read:** `ai/skills/design-systems/distinctive-design-systems`
Define fonts and scale:
```css
:root {
--font-display: 'Orbitron', system-ui;
--font-mono: 'Share Tech Mono', monospace;
--font-sans: 'Inter', system-ui;
--typo-scale: 0.88; /* Mobile */
}
@media (min-width: 640px) {
:root { --typo-scale: 1; }
}
```
### Typography Patterns
```css
/* Magazine-style numbers */
.metric { font-weight: 800; letter-spacing: -0.02em; font-variant-numeric: tabular-nums; }
/* Labels */
.label { text-transform: uppercase; letter-spacing: 0.1em; font-weight: 700; }
```
---
## Step 4: Surface Components
**Read:** `ai/skills/design-systems/design-system-components`
Build layered surface primitives with CVA:
```tsx
const surfaceVariants = cva(
'rounded-lg backdrop-blur-sm transition-colors',
{
variants: {
layer: {
panel: 'bg-tone-cadet/40 border border-tone-jordy/10',
tile: 'bg-tone-midnight/60 border border-tone-jordy/5',
chip: 'bg-tone-cyan/10 border border-tone-cyan/20 rounded-full',
},
},
}
);
export function Surface({ layer, children }: SurfaceProps) {
return <div className={surfaceVariants({ layer })}>{children}</div>;
}
```
---
## Step 5: Motion Tokens
**Read:** `ai/skills/design-systems/distinctive-design-systems`
Define consistent animation timing:
```javascript
// tailwind.config.ts
keyframes: {
'shimmer': { '0%': { backgroundPosition: '200% 0' }, '100%': { backgroundPosition: '-200% 0' } },
'pulse-glow': { '0%, 100%': { opacity: '1' }, '50%': { opacity: '0.5' } },
'slide-in': { '0%': { opacity: '0', transform: 'translateY(10px)' }, '100%': { opacity: '1', transform: 'translateY(0)' } },
},
animation: {
'shimmer': 'shimmer 1.5s ease-in-out infinite',
'pulse-glow': 'pulse-glow 1.8s ease-in-out infinite',
'slide-in': 'slide-in 0.2s ease-out',
}
```
---
## Step 6: Loading States
**Read:** `ai/skills/design-systems/loading-state-patterns`
Create skeleton components that match your aesthetic:
```tsx
export function Skeleton({ className }: { className?: string }) {
return (
<div
className={cn(
'rounded-md bg-muted animate-shimmer',
'bg-gradient-to-r from-muted via-muted-foreground/10 to-muted bg-[length:200%_100%]',
className
)}
/>
);
}
```
---
## Component Skills Reference
| Skill | Purpose |
|-------|---------|
| `distinctive-design-systems` | Aesthetic foundation, tokens |
| `design-system-components` | Surface primitives, CVA |
| `animated-financial-display` | Number animations |
| `loading-state-patterns` | Skeletons, shimmer |
| `financial-data-visualization` | Chart theming |
---
## File Structure
```
styles/
├── globals.css # CSS variables, base styles
├── design-tokens.ts # TypeScript exports
└── theme.css # Component patterns
tailwind.config.ts # Token integration
components/
├── ui/
│ ├── surface.tsx # Surface primitive
│ ├── skeleton.tsx # Loading states
│ └── button.tsx # Variant components
```
---
## NEVER Do
- **Never start with code before documenting aesthetic** — Vibes before CSS
- **Never use pure black (#000) as base** — Always use tinted blacks for depth
- **Never use pure white (#fff) for text** — Use tinted whites that match the palette
- **Never skip design tokens in favor of hardcoded values** — Tokens prevent drift
- **Never create components without variant system** — Use CVA or similar for consistency
- **Never use Inter/Roboto for headings** — Display fonts create distinctiveness
- **Never use default Tailwind colors** — Define your own palette
- **Never skip backdrop-filter blur on glass** — Glass panels need blur to work
- **Never apply decorative patterns to readable content** — Background decoration only
- **Never use high-saturation colors without opacity** — Modulate with rgba()
---
## Checklist
- [ ] Document aesthetic foundation (vibe, inspirations, emotions)
- [ ] Create color token system (CSS + Tailwind + TS)
- [ ] Define typography stack and scale
- [ ] Build Surface primitive component
- [ ] Add motion tokens and animations
- [ ] Create loading state components
- [ ] Document anti-patterns (what NOT to do)Related Skills
tailwind-design-system
No description provided.
responsive-design
No description provided.
frontend-design
Create distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Focuses on creative direction and memorable design choices.
web-design
CSS implementation patterns for layout, typography, color, spacing, and responsive design. Complements ui-design (fundamentals) with code-focused examples.
ui-design
Comprehensive UI design skill covering fundamentals, patterns, and anti-patterns. Layout, typography, color, spacing, accessibility, motion, and component design. Use when building any web interface, reviewing design quality, or creating distinctive UIs.
distinctive-design-systems
Patterns for creating design systems with personality and distinctive aesthetics. Covers aesthetic documentation, color token architecture, typography systems, layered surfaces, and motion. Use when building design systems that go beyond generic templates. Triggers on design system, design tokens, aesthetic, color palette, typography, CSS variables, tailwind config.
design-system-patterns
Foundational design system architecture — token hierarchies, theming infrastructure, token pipelines, and governance. Use when creating design tokens, implementing theme switching, setting up Style Dictionary, or establishing multi-brand theming. Triggers on design tokens, theme provider, Style Dictionary, token pipeline, multi-brand theming, CSS custom properties architecture.
design-system-components
Patterns for building design system components using Surface primitives, CVA variants, and consistent styling. Use when building reusable UI components that follow design token architecture. Triggers on Surface component, CVA, class-variance-authority, component variants, design tokens.
api-design-principles
No description provided.
api-design
REST and GraphQL API design principles — resource modeling, HTTP semantics, pagination, error handling, HATEOAS, schema design, and DataLoader patterns. Use when designing new APIs, reviewing specs, or establishing team API standards.
schema-markup
Add, fix, or optimize schema markup and structured data. Use when the user mentions schema markup, structured data, JSON-LD, rich snippets, schema.org, FAQ schema, product schema, review schema, or breadcrumb schema.
prompt-engineering
Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, designing production prompt templates, or building AI-powered features.