design-md

Define design tokens with rationale in a single DESIGN.md file.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Harries/hermes-agent --skill design-md-harries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-md
Source: https://github.com/Harries/hermes-agent/tree/main/skills/creative/design-md
Command: npx skills add https://github.com/Harries/hermes-agent --skill design-md-harries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DESIGN.md provides a single-file specification that combines YAML tokens and rationale for design systems, enabling consistent, machine-readable design tokens and human-friendly rationale in one file.

Core Features & Use Cases

  • Lint, diff, and export tokens for design systems to ensure consistency across projects.
  • Port tokens between projects, audit accessibility and WCAG compliance, and generate UI tokens for implementation.
  • Use cases include creating a token-driven design system, porting design rules between projects, and exporting Tailwind-like or DTCG formats.

Quick Start

Create DESIGN.md in your project root with tokens and rationale, then run the CLI to lint or export.

Frequently Asked Questions about design-md

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

FAQPage Schema
What is a DESIGN.md file and how does it manage design tokens?

A DESIGN.md file is a single-file design specification coupling YAML design tokens with human-friendly rationale. It provides machine-readable token definitions and Markdown documentation together to maintain consistency across projects.

How do I export design tokens to Tailwind or DTCG formats?

You can export design tokens to Tailwind or DTCG formats by running the CLI on a DESIGN.md file. The file requires a YAML frontmatter with version, name, and tokens, plus a descriptive Markdown body to process the export.

Can I diff and lint design tokens across different projects?

Yes, you can lint and diff design tokens across different projects using the CLI. It audits token consistency, checks WCAG accessibility compliance, and helps port design rules between different project environments.

Do I need YAML frontmatter to validate a design system specification?

Yes, YAML frontmatter containing version, name, and tokens is required to validate a design system. The linter checks this structure to ensure your design tokens are consistent and machine-readable.

What is the best way to audit WCAG compliance for design tokens?

The best way to audit WCAG compliance is using the DESIGN.md linter on your token definitions. It checks accessibility rules directly against the YAML tokens and rationale to ensure standards compliance.