https://fluent2.microsoft.design/design-tokens

What this source teaches

  • Compare global→alias token mapping with AwesomeDS token architecture for cross-platform consistency.
  • Enforce a lintable ban on raw color/spacing values where a semantic token exists.
  • Document platform-specific token mapping exceptions explicitly.

Where AwesomeDS applied it

Implementations and artifacts

No directly linked artifacts.

Caveats & anti-imitation

Transfer global→alias token architecture and raw-value ban patterns; do not import Microsoft product token names or brand colors.

Evidence: first-party-guidance · Verified 2026-07-16 · Cadence 90d