design

To create a unified SaaS design system, use CREATE mode to generate a centralized design-system.md file documenting colors, typography, spacing, tokens, and component patterns. This serves as a single source of truth to keep UI consistent across projects and eliminate design drift.

Updating existing design tokens and component patterns is handled through MODIFY mode. It reconciles and updates your instructions/design-system.md file to ensure UI patterns stay consistent across your product while maintaining centralized governance over all design decisions.

Yes, you can enforce an established design system using WORK WITHIN mode. It ensures typography, spacing, colors, and component usage stay aligned with your existing guidelines when building new features, preventing UX drift and maintaining visual consistency.

This design system generator outputs documentation, specifically an instructions/design-system.md file. It documents colors, typography, spacing, tokens, and component patterns while providing usage guidelines, serving as a centralized repository rather than generating executable component code.

To extract design tokens from existing code, use CREATE mode to extract patterns from your current references. It generates a comprehensive design-system.md file that formalizes your colors, typography, and spacing into a unified set of documented design tokens and component patterns.

Using markdown for design system governance provides centralized documentation but relies on manual enforcement. The design-system.md file serves as a reference for colors, typography, and component patterns, but it does not automatically validate or block non-compliant UI code during development.