design-md

Name: design-md
Availability: InStock
Author: aissenliu

Validate DESIGN.md files and export design tokens to Tailwind or DTCG JSON.

Updated Apr 27, 2026

Search Tags:#design #diff #tokens #lint #design-system #export #design-tokens

Ready to run

npx skills add https://github.com/AissenLiu/EasyHermes --skill design-md-aissenliu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-md
Source: https://github.com/AissenLiu/EasyHermes/tree/main/hermes-agent/skills/creative/design-md
Command: npx skills add https://github.com/AissenLiu/EasyHermes --skill design-md-aissenliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DESIGN.md consolidates design tokens and rationale into a single, machine-readable file, enabling automated validation, versioning, and cross-project consistency.

Core Features & Use Cases

Lint: validate structure and token references.
Diff: compare design specs across versions to detect regressions.
Export: transform tokens into Tailwind or DTCG formats for implementation pipelines.
Rationale: include human-readable reasoning to guide design decisions.

Quick Start

Create a DESIGN.md for your design system that combines tokens and rationale in one file.

Frequently Asked Questions about design-md

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

FAQPage Schema

How do I export design tokens to Tailwind or W3C formats from a markdown file?▼

You can export design tokens to Tailwind or W3C DTCG formats by validating a DESIGN.md file that combines tokens and rationale into a machine-readable specification. This process enforces canonical frontmatter fields like version, name, and tokens to ensure structured output.

What is the best way to lint design tokens and validate references in a design system?▼

Linting design tokens involves validating the structure and token references within a DESIGN.md file. This ensures your design system enforces canonical frontmatter fields and detects invalid token references before exporting to implementation pipelines.

How do I diff design token versions to detect regressions across multiple projects?▼

Diffing design token versions compares design specs across versions to detect regressions in multi-project environments. By structuring tokens in DESIGN.md, you can track version changes and compare token differences systematically.

Can I preserve human-readable rationale when converting design tokens to machine-readable formats?▼

Yes, converting design tokens to machine-readable formats preserves human-readable rationale within the DESIGN.md file. This approach consolidates token definitions and reasoning, enabling automated validation while guiding design decisions.

What frontmatter fields are required to structure design tokens for automated versioning?▼

Structuring design tokens for automated versioning requires canonical frontmatter fields including version, name, and tokens. These fields validate the DESIGN.md structure and enable automated diffing across multiple design system projects.