design-md-validator

To validate a DESIGN.md file, lint it against the official Google design specification to identify structural, token, and accessibility issues. The validator requires the @google/design.md CLI through npx and uses runtime rule discovery to provide current lint results.

Yes, design system validation checks WCAG contrast issues, broken references, missing tokens, and typography gaps. It detects orphaned tokens and section-order problems to ensure full structural and accessibility compliance.

Yes, token workflows support exporting design tokens to Tailwind, CSS custom properties, or DTCG formats. You can also compare design system versions to track token changes and resolve reference discrepancies across updates.

You do not need a permanent local installation; the validator executes the @google/design.md CLI through npx. This runtime rule discovery mechanism ensures current lint results and reliable remediation guidance without manual CLI management.

The best way to audit a remote DESIGN.md document is to run a full validation check against the Google specification. This identifies invalid references and contrast failures, then provides actionable fixes you can apply and re-validate.

Design system validation fails on missing tokens and section-order problems because the linter enforces the official Google DESIGN.md specification structure. It flags orphaned tokens and typography gaps to prevent broken references during implementation.