design-md

Lint, diff, and export DESIGN.md token files to Tailwind or DTCG formats.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DESIGN.md tokens play a critical role in codifying design intent, but teams struggle to keep them consistent, validated, and exportable across projects.

Core Features & Use Cases

  • Lint and diff DESIGN.md files to ensure correct structure, token references, and versioning.
  • Export tokens to Tailwind and W3C DTCG JSON formats for design-system interoperability.
  • Use cases include maintaining design-system parity, auditing token coverage, and porting styles between projects.

Quick Start

Create or update the DESIGN.md file, then run the lint tool to validate structure and references, and finally use the export feature to generate Tailwind or DTCG outputs.

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 in a DESIGN.md file?

To validate design tokens in a DESIGN.md file, run the lint tool to check structure, token references, and versioning, ensuring your design system maintains correct formatting and consistency across projects.

Can I export design tokens to Tailwind or W3C DTCG JSON?

Yes, you can export design tokens to Tailwind or W3C DTCG JSON formats, generating machine-consumable outputs that resolve token references for reliable design-system interoperability and styling parity.

What is the DESIGN.md format for shared design systems?

The DESIGN.md format is a token specification file that codifies design intent by enforcing structure for version, name, colors, and typography to maintain shared design language across multiple projects.

How do I diff design token files to audit coverage?

You can diff design token files by running the validation tool against your DESIGN.md spec, which compares structure and token references to audit coverage and maintain design-system parity.

Do I need specific dependencies to lint DESIGN.md token specs?

No specific dependencies are required to lint DESIGN.md token specs, as the tool operates directly on your markdown file to validate structure, resolve references, and export to Tailwind or DTCG formats.

Why does my design token export fail token reference resolution?

Design token export fails reference resolution when the DESIGN.md file violates structural rules for version, name, colors, or typography, preventing the reliable generation of machine-consumable Tailwind or DTCG outputs.