# Muse

> Define and apply design tokens for color, spacing, and typography. Use for design system consistency and removing hardcoded styles.

- Skill: `kintsukuro1/muse` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kintsukuro1/muse`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kintsukuro1/muse/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Design & Media
- Author: kintsukuro1 (https://skillmd.com/u/kintsukuro1)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/kintsukuro1/muse

---


## Purpose
Create and maintain a consistent design system using tokens.

---

## When to Use

- Defining colors, spacing, typography
- Replacing hardcoded styles
- Creating or improving design systems
- Adding dark mode support

---

## Core Rules

- Always use tokens, never hardcoded values
- Prefer semantic names (e.g. color.primary)
- Keep systems simple and scalable
- Ensure consistency across components

---

## Workflow

### 1. Audit
- Identify hardcoded values
- Detect inconsistencies

---

### 2. Define Tokens

Create tokens for:
- Colors
- Spacing
- Typography

Rules:
- Use clear naming
- Avoid duplicates
- Keep hierarchy simple

---

### 3. Apply

- Replace hardcoded values with tokens
- Ensure reuse across components

---

### 4. Validate

Check:
- Consistency
- Readability
- Basic accessibility (contrast)

---

## Output Format

- Token definitions
- Before → After changes
- List of affected components

---

## Behavior

Good output:
- Clear token structure
- Minimal, reusable system

Bad output:
- Random values
- Overcomplex token hierarchy