SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsseed-token-analysis

seed-token-analysis

Design & creation

View repository

Updated 10-16 05:05

About this skill

SEED token analysis

Based on the current checkout's packages/rootage/color.yaml, verify the color token's definition, connection relationships, generation results, and contrast. The script does not change files or Git state.

Token map

Specify one color token.

bun skills/seed-token-analysis/scripts/token-map.ts '$color.fg.neutral'

Read the result JSON in the following order.

  1. tokenCheck the canonical과 statethat normalized the input in state는 matched, ambiguous, not-found . It is one of ambiguous면 candidates. Re-run with the exact token from not-found, do not arbitrarily choose a similar name.
  2. definitionCheck the Rootage source path, description, and raw values per mode in
  3. resolvedValues. If a mode's value is missing or an alias could not be resolved all the way through, do not substitute another mode's value.
  4. dependentTokens. This list does not calculate transitive dependencies or the combined effect of multiple changes.
  5. componentUsages.
  6. generatedSurfacesCompare the per-platform and per-package status, actual paths, and expected expectedPaths. missingmeans the generation result was not found, and does not mean you should directly modify the Rootage source.
  7. warningsand check whether it is readOnly가 true.

token.publicNamesIf present, you can check the CSS variable and public name. Use generated files only as evidence for verifying the actual distribution surface, and do not modify them directly.

Contrast check

Specify one foreground token and one or more background tokens. --background와 --themecan be repeated, and if you need the actual color under a semi-transparent background, add --backdrop. If --themeis omitted, both light and dark are checked. Duplicate themes are removed, and results are returned in the order light, dark.

bun skills/seed-token-analysis/scripts/token-contrast.ts \
  --foreground '$color.fg.warning-contrast' \
  --background '$color.bg.warning-solid' \
  --background '$color.bg.warning-solid-pressed' \
  --theme light \
  --theme dark

bun skills/seed-token-analysis/scripts/token-contrast.ts \
  --foreground '$color.fg.neutral' \
  --background '$color.bg.overlay' \
  --theme light \
  --backdrop '$color.bg.layer-default'

source와 request. The result's checksreturns the following status for each background and theme combination.

  • resolved: Alias and color composition were completed, and the WCAG 2.x contrast ratio and pass/fail per criterion were calculated.
  • unresolved: The corresponding mode value or alias could not be resolved. Do not substitute another theme's value.
  • needs-backdrop: The color under the semi-transparent background cannot be determined. Specify an actual opaque backdrop token and check again.

#RRGGBBAAare interpreted as alpha. A semi-transparent foreground is composited over the background before contrast is calculated. A semi-transparent background is first composited over the backdrop, and if the backdrop is also semi-transparent, the calculation is not completed.

Top-level status가 partialdoes not mean all combinations were checked. It is only the lowest value among the minimumRatio는 resolved combinations, and does not include unresolved와 needs-backdrop combinations. wcagEach boolean represents the AA and AAA criteria for normal and large text, and the 3:1 criterion for non-text, respectively. Finally, warningsand check readOnly가 true.

Task connections and boundaries

  • This skill handles only color tokens. It does not analyze other token types such as dimension, typography, or shadow.
  • The token map looks up only one token at a time. Contrast checks can compare one foreground against multiple backgrounds, but they do not compute the combined effect of multiple changes.
  • Running the same command before and after changing a token lets you check the difference between the source and the generated surfaces. If a change is needed, modify the Rootage source and follow the repository's generation procedure.
  • The impact of multiple tokens or an actual diff on packages, platforms, and verification order is checked with seed-change-plan.
  • Release bumps and changesets for public packages are finalized in seed-changeset. Do not decide the bump based only on this skill's usage sites or generated surfaces.