verify-design-tokens

Use this validation to enforce design token architecture by verifying Layer 3 components import only from Layer 2 or the public API. This prevents direct primitive or semantic imports, ensuring consistent token strategy and catching regressions early.

The 3-layer design token architecture structures tokens from Primitives to Semantic to Components. It enforces token consumption through a public API rather than direct imports, maintaining consistent strategy and facilitating cross-team design-system alignment.

Validate migrated components by checking that they consistently reference design tokens via the public API. The process verifies token usage and migration coverage, reporting deviations and guiding remediation to ensure strict architecture compliance.

Yes, this design token validation applies to frontend projects using the design-tokens library. It checks the codebase to confirm Layer 3 imports and migrated components adhere to the architecture rules outlined in the migration guide and references.

Migrated components show direct primitive token imports when they deviate from the 3-layer architecture. The validation identifies incorrect import paths and reports them as deviations, guiding remediation to ensure tokens are consumed only through the public API.