design-md

To generate a design system document from Stitch project tokens, synthesize screen metadata, colors, typography, and spacing into a DESIGN.md file. This codifies the project's design language into a single source of truth for team onboarding and consistency.

The best way to document design tokens for new Stitch screens is to extract color, typography, and spacing values and translate them into a semantic DESIGN.md. This translates technical CSS and Tailwind values into designer-friendly language to guide future screen generation.

Yes, you can use it to extract semantic design language from existing Stitch MCP outputs. The process requires accessible screen metadata and token data to successfully synthesize the project's design system into a structured document.

Yes, accessible screen metadata is required to codify a design language in DESIGN.md. The synthesis process depends on extracting color, typography, and spacing tokens from these accessible Stitch project assets to generate an accurate design-system narrative.

Your Stitch project lacks a cohesive design-system narrative because technical token values are not translated into designer-friendly language. Generating a DESIGN.md structures these screen-level tokens into a semantic document that maintains consistency and guides onboarding.

You should update your design system documentation when starting a new Stitch screen or modifying existing design tokens. Generating an updated DESIGN.md ensures the new screens align with the project’s established semantic design language and technical token values.