groundx-design-standards

Design tokens act as a centralized source of truth for color, typography, and spacing. Medium-specific skills consume autogenerated mirrors from a canonical tokens.json file to enforce brand fidelity across web, slides, and documents.

To update brand guidelines, modify the canonical tokens.json file and run the standard mirrors generator. This propagates token changes to all medium-specific skills, ensuring brand invariants remain synchronized across all outputs.

Brand invariants are the core visual rules for color, typography, and logos. You need to document them when setting up CI pipelines to automatically verify design drift and enforce brand guidelines across all generated media.

Yes, a canonical tokens.json file serves as the single source of truth for your design language. Medium-specific skills auto-generate and consume mirrors from this file to maintain strict brand consistency across web and slide outputs.

Brand style-guide drift occurs when medium-specific implementations lack a centralized source of truth. Using a canonical tokens.json file to autogenerate mirrors for each medium prevents this drift and maintains brand fidelity.

The best way to structure design tokens is using a machine-readable tokens.json file paired with narrative references. This separates values from rationale while allowing medium-specific skills to consume autogenerated mirrors for consistency.