Muse

Defines and audits design tokens to replace hardcoded UI values across apps.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Dinxeshh/agent-skills --skill muse-dinxeshh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Muse
Source: https://github.com/Dinxeshh/agent-skills/tree/main/skills/muse
Command: npx skills add https://github.com/Dinxeshh/agent-skills --skill muse-dinxeshh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Muse eliminates inconsistent styling by defining and managing design tokens so teams stop patching components with hardcoded values and mismatched spacing, colors, or typography.

Core Features & Use Cases

  • Token definition & lifecycle: Capture colors, spacing, typography, shadows, and radius in semantic tokens with adoption tracking and migration guidance.
  • Token application & audits: Replace hardcoded UI values, ensure contrast, grid alignment, and dark mode readiness while honoring Palette, Flow, Showcase, and Judge feedback.
  • Design system foundation: Build reusable systems that feed Artisan, Loom, Flow, and Showcase, documenting decisions for accessible, consistent experiences.

Quick Start

Use Muse to audit the current stack for hardcoded spacing or colors and output the semantic tokens plus migration notes needed for dark mode support.

Frequently Asked Questions about Muse

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

FAQPage Schema
How do I replace hardcoded color and spacing values with design tokens?

To replace hardcoded UI values, define semantic tokens for colors, spacing, and typography, then apply them across your apps. This process audits your current stack and generates migration notes to ensure consistent, lifecycle-aware styling.

What are semantic design tokens and when do I need them?

Semantic design tokens are contextual variables capturing colors, spacing, and typography that adapt to themes like dark mode. You need them when patching components with mismatched values or building a reusable design system foundation.

How do I audit my UI for dark mode readiness and contrast accessibility?

You audit UI for dark mode readiness by reviewing hardcoded colors and spacing against accessibility contrast requirements. This generates lifecycle-aware semantic tokens covering both light and dark modes to ensure proper theme support.

Can I use this to build a reusable design system foundation from scratch?

Yes, you can build a reusable design system foundation by defining semantic tokens for typography, shadows, radius, and spacing. This establishes consistent, accessible experiences and documents decisions for downstream component libraries.

What is the best way to manage token lifecycle and migration during a design system rebuild?

The best way to manage token lifecycle is capturing values in semantic tokens with adoption tracking and migration guidance. This ensures smooth transitions during design system rebuilds while honoring palette and accessibility feedback.

Why does my UI have inconsistent styling and mismatched spacing across components?

Inconsistent styling occurs when teams patch components with hardcoded values instead of using managed design tokens. Defining semantic tokens for spacing, colors, and typography eliminates mismatches and ensures grid alignment.