design-md

Define and validate design tokens in a DESIGN.md file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The DESIGN.md skill enables consistent, machine- and human-readable design system definitions by combining YAML tokens with Markdown rationale, and provides linting, diffing, and export capabilities for design systems.

Core Features & Use Cases

  • Lint DESIGN.md for structure, token references, and WCAG contrast.
  • Diff versions to detect regressions in tokens or typography.
  • Export tokens to Tailwind or DTCG JSON for downstream tooling.

Quick Start

Create a DESIGN.md in your project root that defines tokens and styles, then use the skill to lint, diff, and export.

Frequently Asked Questions about design-md

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

FAQPage Schema
How do I validate design tokens for WCAG compliance in a Markdown file?

You can lint a DESIGN.md file to validate its structure, token references, and WCAG contrast. This workflow checks your YAML frontmatter, token types, and canonical sections to ensure design system consistency.

Can I export design tokens to Tailwind or DTCG JSON from Markdown?

Yes, you can export design tokens to Tailwind or DTCG JSON. The skill processes your DESIGN.md file and generates outputs for downstream tooling, enabling consistent branding across multiple projects.

What is the best way to track design token regressions across versions?

The best way to track design token regressions is to use the diff workflow on your DESIGN.md file. This process compares versions to detect changes in tokens or typography, preventing unintended visual regressions.

Do I need YAML frontmatter to define a design system in Markdown?

Yes, you need YAML frontmatter to define a design system in Markdown. The DESIGN.md skill requires specific name and description fields, alongside token types and canonical sections, to establish a machine-readable source of truth.

How does combining YAML tokens with Markdown rationale improve design systems?

Combining YAML tokens with Markdown rationale improves design systems by creating a single source of truth that is both machine-readable for automated linting and human-readable for design context and decision tracking.

What should a DESIGN.md file include to pass lint checks?

To pass lint checks, a DESIGN.md file should include YAML frontmatter with name and description, defined token types, canonical sections, and properly formatted token references for WCAG contrast validation.