What problem does it solve?
Design system maintainers need to understand how a single color token flows from its Rootage definition through mode-specific aliases into components and generated platform packages, and whether foreground/background combinations meet WCAG 2.x contrast requirements, without manually tracing YAML files and generated artifacts.
Core Features & Use Cases
- Token Mapping: Resolves one color token's canonical ID, per-mode raw values, alias chains to final hex colors, direct dependent tokens, structured component usages (variant, state, slot, property), and presence across generated surfaces (CSS, Qvism, Tailwind 3/4, Lynx).
- Contrast Checking: Computes WCAG 2.x contrast ratios for one foreground token against multiple background tokens across light and dark themes, compositing translucent colors over explicit backdrops and reporting AA/AAA pass states.
- Use Case: Before changing
$color.fg.neutral, run the token map to see every component and generated package that references it, then run the contrast check against its backgrounds in both themes to confirm the new value still passes AA for normal text.
Quick Start
Ask the assistant to analyze the SEED color token $color.fg.neutral and check its WCAG contrast against $color.bg.layer-default in light and dark themes.