What problem does it solve?
Updating design tokens in the Spectrum Web Components monorepo involves two distinct workflows—custom token changes versus an @adobe/spectrum-tokens package version bump—and running the wrong one (or only part of one, like just yarn tokens:update) silently skips deleted-token curation and broken token() reference fixes.
Core Features & Use Cases
- Workflow Dispatch: Determines whether a request is a custom-tokens-only change or an @adobe/spectrum-tokens version bump, asking the user when ambiguous instead of guessing.
- Single Source of Truth: Reads the canonical steps from
2nd-gen/packages/tools/swc-tokens/README.md fresh on every run rather than duplicating them, preventing documentation drift.
- Use Case: A developer bumps
@adobe/spectrum-tokens in package.json and asks to update tokens; the Skill routes to the seven-step upgrade section of the README, ensuring deleted-token curation in custom/deleted.json and CSS token() reference fixes are not skipped.
Quick Start
Ask the assistant to update the design tokens or bump the @adobe/spectrum-tokens package, and it will route you through the correct documented workflow.