0.3.0

Bumps version from 0.2.0 to 0.3.0. All changes since 0.2.0:

Bug Fixes

• Nested token declarations no longer crash the linter. Nested YAML like colors: { background: { light: '#fff' } } is now parsed correctly with dot-separated paths (e.g. colors.background.light). (#103, @vikks)
• Non-string YAML values no longer crash the linter. Spacing values like unit: 8 (parsed as a number by YAML) previously caused raw.match is not a function. The type guard in parseDimensionParts now handles this. (#79, @SyedaQurratAI) Fixes #106.
• Boolean YAML scalars in component props no longer crash the linter. (#94)
• lint --format markdown now renders the report correctly instead of printing [object Object]. (#95)
• Tailwind v4 export handles digit-prefixed token names. (#72, @Bortlesboat)
• Removed stale dependencies (ink, react, etc.) and fixed lint scripts. (#98)

Features

• Unknown top-level key warnings. The linter now reports a warning when the frontmatter contains keys not recognized by the spec. (#84, @ryo-manba)
• Nested token support. Colors, spacing, and rounded tokens support arbitrary nesting depth with dot-separated symbol table paths. (#103, @vikks)

Docs

• Added PHILOSOPHY.md. (#99)
• Documented Windows/PowerShell npx invocation. (#104, @mvanhorn)
• Updated color spec to document all supported CSS color formats. (#96)

Contributors

Thank you to the contributors who made this release possible:

• @vikks (#103)
• @SyedaQurratAI (#79)
• @ryo-manba (#84)
• @Bortlesboat (#72)
• @mvanhorn (#104)

0.2.0

Changelog

[0.2.0] — 2026-05-26

Added

• Tailwind CSS v4 export — New --format css-tailwind emits a CSS @theme { ... } block using Tailwind v4's native CSS-variable token namespaces (--color-*, --font-*, --text-*, --leading-*, --tracking-*, --font-weight-*, --radius-*, --spacing-*). (#45) — by @sbrsubuvga
• CSS Color Module format support — The validator and linter now accept standard and CSS Color Module color formats. (#73) — by @dalmaer
• Windows-friendly designmd bin alias — The dot-free designmd alias resolves cleanly via PATHEXT on Windows, where the original design.md shim was opened as a Markdown file instead of being executed. (#62) — by @voidborne-d
• Component token diff — The diff command now includes component changes (button styles, added/removed component tokens) that were previously silently skipped. (#51) — by @Saatvik-GT

Changed

• Renamed Tailwind export formats for clarity and backwards compatibility: css-tailwind (v4 CSS), json-tailwind (v3 JSON), and tailwind is preserved as a backwards-compatible alias for json-tailwind. (#64)

Fixed

• Orphaned-token false positives — MD3 paired tokens (e.g. on-primary, primary-container) and baseline families are no longer flagged as orphans when a sibling token is in use. (#59) — by @mvanhorn
• Numeric component property crash — Properties like fontWeight: 600 no longer crash the model handler when passed to string-only validation functions. (#43) — by @tejas55bk
• Transparent hex colors — 8-digit hex colors with alpha (e.g. #FFFFFF00) are now supported. (#24) — by @tototofu123
• Token reference resolution — References in rounded and spacing sections are now resolved correctly. (#26) — by @tejas55bk

Maintenance

• Updated GitHub Actions checkout from v4 to v6. (#58) — by @christianoliff
• Clarified npm install instructions on Windows and added a registry smoke test to CI. (#57) — by @camilojheans

New Contributors

• @sbrsubuvga made their first contribution in #45
• @camilojheans made their first contribution in #57
• @Saatvik-GT made their first contribution in #51
• @tejas55bk made their first contribution in #43
• @voidborne-d made their first contribution in #62
• @christianoliff made their first contribution in #58
• @mvanhorn made their first contribution in #59
• @tototofu123 made their first contribution in #24

0.1.1

Release Notes: @google/design.md v0.1.1

This is a patch release updating the documentation to correctly reflect the available CLI commands.

---

📝 Documentation Updates

• Updated Command References: Replaced documentation for the outdated tailwind command with the correct export command.
• Clarified Interoperability: Documented how to use export to generate both Tailwind CSS themes and DTCG tokens:

  npx @google/design.md export --format tailwind DESIGN.md > tailwind.theme.json
  npx @google/design.md export --format dtcg DESIGN.md > tokens.json

0.1.0: chore: packaging for release (#11)

Release Notes: @google/design.md v0.1.0

We are excited to announce the initial open-source release of @google/design.md, an agent-first CLI and linter for the DESIGN.md format. This tool bridges the gap between design systems and code by providing a formal, machine-readable way to validate and compile design tokens documented in markdown.

---

🚀 Features

• Design System Linter: Validates DESIGN.md files against the formal spec, catching unresolved references, circular dependencies, and invalid token values.
• Spec Generator: Generates human-readable specification documentation from the core schema.
• Agent-First Design: Deterministic JSON output and silent execution modes optimized for AI agents performing design system maintenance.

🛠 Improvements & Fixes

• Clean JSON Output: Purged debug logging to ensure output is pure JSON and safe for piping to other tools or AI agents.
• Windows Shell Compatibility: Added designmd binary alias to prevent Windows from confusing the .md extension with a file association.
• Startup Reliability: Resolved module loading issues that could cause crashes on import.
• Self-Contained Package: Optimized the package to be self-contained, reducing install size and avoiding dependency conflicts.

---

📦 Installation

Install globally via npm or bun:

npm install -g @google/design.md
# or
bun add -g @google/design.md

Or run directly via npx:

npx @google/design.md lint DESIGN.md

(Windows users: use npx designmd if file extension associations cause issues).