본문으로 건너뛰기
cccskills
무료GitHub에 공개

design-intelligence

Design system bootstrapping and token generation. Takes project context and outputs ready-to-use design tokens, Tailwind config, and CSS variables.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md7.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Design Intelligence — Token Generation & Design System Bootstrapping

This skill helps set up design systems from scratch. Give it your project context (industry, brand, users) and it generates ready-to-use design tokens with Tailwind config snippets and CSS variable files.

When to Use

  • Setting up a new project's design system (/spartan:ux system)
  • Choosing color palettes for a specific industry/brand
  • Generating typography scales
  • Creating spacing systems
  • Bootstrapping a component inventory

What This Skill Does

  1. Takes project context (what, who, industry, personality)
  2. Generates a complete design token set
  3. Outputs in 3 formats: token reference doc, Tailwind config, CSS variables
  4. Creates a component inventory based on the project type

How It Works

Step 1: Gather Context

Ask these questions (skip any the user already answered):

  1. What are you building? (dashboard, SaaS, marketplace, mobile app, landing page, etc.)
  2. Who uses it? (developers, business users, consumers, admins)
  3. What's the personality? Pick 2-3:
    • Clean / Professional / Corporate
    • Bold / Playful / Creative
    • Minimal / Technical / Developer-focused
    • Warm / Friendly / Approachable
    • Premium / Luxury / Refined
    • Data-heavy / Dense / Information-rich
  4. Light, dark, or both?
  5. Any brand colors already decided? (if yes, use those as the foundation)
  6. Reference apps? (apps that have the quality you want)

Step 2: Generate Color Palette

Based on the context, generate a complete palette:

For dark themes:

Background:     #0F172A (slate-900 family)
Surface:        rgba(30, 41, 59, 0.5) (glass effect)
Primary:        [based on personality — blue for professional, green for growth, etc.]
Primary Hover:  [10% darker]
Accent:         [complementary or analogous — use sparingly, max 10-15%]
Text:           #F8FAFC (near white)
Text Secondary: #94A3B8 (slate-400)
Text Muted:     #64748B (slate-500)
Border:         rgba(148, 163, 184, 0.1)
Success:        #22C55E
Warning:        #F59E0B
Error:          #EF4444

For light themes:

Background:     #FFFFFF or #F8FAFC
Surface:        #FFFFFF
Primary:        [based on personality]
Primary Hover:  [10% darker]
Accent:         [complementary]
Text:           #0F172A (near black)
Text Secondary: #475569 (slate-600)
Text Muted:     #64748B (slate-500)
Border:         #E2E8F0 (slate-200)
Success:        #16A34A
Warning:        #D97706
Error:          #DC2626

Color selection by personality:

PersonalityPrimary rangeAccent range
Professional / CorporateBlue (#2563EB → #1E40AF)Slate or Amber
Bold / CreativePurple (#7C3AED), Pink (#EC4899)Yellow or Cyan
Minimal / TechnicalGray (#374151), Black (#111827)One bright accent
Warm / FriendlyOrange (#EA580C), Teal (#0D9488)Amber or Rose
Premium / LuxuryDeep Blue (#1E3A5F), Gold (#B8860B)Silver or Champagne
Data-heavyNeutral blue (#3B82F6)Green for positive, Red for negative

Step 3: Generate Typography Scale

Pick a font pairing based on personality:

PersonalityFont recommendationWhy
ProfessionalDM Sans, Plus Jakarta SansClean geometric, good for UI
TechnicalJetBrains Mono (code) + Inter (UI)Developer-friendly
CreativeOutfit, Space GroteskDistinctive but readable
WarmNunito, QuicksandRounded, friendly feel
PremiumPlayfair Display (headings) + Lato (body)Elegant contrast
Data-heavyInter, Roboto Mono (numbers)Tabular nums, high readability

Type scale (base 16px):

h1: 36px / 700 / 1.2 line-height
h2: 30px / 700 / 1.25
h3: 24px / 600 / 1.3
h4: 20px / 600 / 1.35
h5: 18px / 600 / 1.4
h6: 16px / 600 / 1.4
body: 16px / 400 / 1.6
body-sm: 14px / 400 / 1.5
caption: 12px / 500 / 1.4

Step 4: Generate Spacing & Radius

Spacing scale (8px base):

xs:   4px   (0.25rem)
sm:   8px   (0.5rem)
md:   16px  (1rem)
lg:   24px  (1.5rem)
xl:   32px  (2rem)
2xl:  48px  (3rem)
3xl:  64px  (4rem)

Radius by personality:

PersonalityCardButtonBadgeInput
Professional8px6px4px6px
Minimal0-4px4px2px4px
Friendly12-16px8px9999px8px
Premium12px8px6px8px

Shadow by personality:

PersonalityStyle
ProfessionalSubtle: 0 1px 3px rgba(0,0,0,0.1)
MinimalNone or very subtle borders
FriendlySoft: 0 4px 12px rgba(0,0,0,0.08)
PremiumLayered: 0 1px 2px rgba(0,0,0,0.06), 0 4px 12px rgba(0,0,0,0.08)
Dark themeGlow: 0 0 20px rgba(primary, 0.15)

Step 5: Output in 3 Formats

Format 1: Token Reference Doc (.planning/design/system/tokens.md)

Human-readable markdown with all tokens, used by designers and all commands.

Format 2: Tailwind Config Snippet

// Paste into tailwind.config.ts → theme.extend
{
  colors: {
    primary: '[value]',
    'primary-hover': '[value]',
    accent: '[value]',
    background: '[value]',
    surface: '[value]',
    // ... all color tokens
  },
  fontFamily: {
    sans: ['[font]', 'sans-serif'],
  },
  borderRadius: {
    card: '[value]',
    button: '[value]',
  },
  boxShadow: {
    card: '[value]',
  },
}

Format 3: CSS Variables

:root {
  /* Colors */
  --color-primary: [value];
  --color-primary-hover: [value];
  --color-accent: [value];
  --color-bg: [value];
  --color-surface: [value];
  --color-text: [value];
  --color-text-secondary: [value];
  --color-text-muted: [value];
  --color-border: [value];
  --color-success: [value];
  --color-warning: [value];
  --color-error: [value];

  /* Typography */
  --font-family: '[font]', sans-serif;
  --font-size-h1: 36px;
  /* ... full scale */

  /* Spacing */
  --space-xs: 4px;
  --space-sm: 8px;
  --space-md: 16px;
  --space-lg: 24px;
  --space-xl: 32px;

  /* Radius */
  --radius-card: [value];
  --radius-button: [value];
  --radius-badge: [value];

  /* Shadows */
  --shadow-sm: [value];
  --shadow-md: [value];
  --shadow-lg: [value];
}

Step 6: Generate Component Inventory

Based on the project type, list the components needed:

Dashboard / SaaS:

  • Sidebar navigation, Top bar, Stat cards, Data tables, Charts, Modals, Forms, Toast notifications, Dropdown menus, Badges, Avatars, Breadcrumbs

Marketplace / E-commerce:

  • Product cards, Search bar, Filters, Cart, Checkout form, Reviews, Ratings, Image galleries, Price displays, Category navigation

Mobile app:

  • Bottom tab bar, Pull-to-refresh, Swipeable cards, Action sheets, Floating action button, List items, Empty states, Onboarding screens

Landing page:

  • Hero section, Feature grid, Testimonials, Pricing table, CTA buttons, Footer, Navigation, Social proof

Save component inventory to .planning/design/system/components.md.


Design System Constraint for Code Generation

When generating UI code and design tokens already exist:

Read .planning/design/system/tokens.md or .planning/design-config.md FIRST. Your code MUST use these tokens. Do NOT use Tailwind defaults, generic colors, or made-up spacing.

Think of it like a jazz musician: the chord progression is set (tokens). Your job is to build beautifully within it. Don't change the key.


Checklist Before Delivering

  • All 3 output formats generated (token doc, Tailwind, CSS variables)
  • Colors have enough contrast (4.5:1 for text)
  • Typography scale is consistent and readable
  • Spacing uses the grid (no arbitrary values)
  • Component inventory matches project type
  • design-config.md updated (if it existed before)

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Creates RPC-style endpoint following layered architecture (Controller → Manager → Repository). Use when creating new API endpoints or CRUD operations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

Write blog posts, guides, tutorials, and long-form content. Sounds like a real person, not AI. Use when the user wants polished written content.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

Design RPC-style APIs with layered architecture (Controller → Manager → Repository). Use when creating new API endpoints, designing API contracts, or reviewing API patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

Run a structured brainstorm session for startup ideas. Takes a theme or problem and generates ideas with quick gut-checks. Use when the user wants to explore a space or generate new ideas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

Run real browser QA with Playwright. Use when testing a frontend feature, verifying UI before PR, smoke testing after deploy, or investigating reported visual bugs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

CI/CD pipeline patterns for GitHub Actions, PR automation, and deployment workflows. Use when setting up CI, fixing broken pipelines, automating PR checks, or configuring deployment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

c0x12c의 스킬 모두 보기

이 스킬의 문제 신고