token-update
/token-update
Dispatches to the correct design token update workflow (custom tokens only vs @adobe/spectrum-tokens version bump). Use whenever asked to update, bump, or upgrade design tokens, or when told to run a token update.
- Author
- adobe ↗
- Repository
- spectrum-web-components ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Dispatches to the correct design token update workflow (custom tokens only vs @adobe/spectrum-tokens version bump). Use whenever asked to update, bump, or upgrade design tokens, or when told to run a token update.
Original author description
Dispatches to the correct design token update workflow (custom tokens only vs @adobe/spectrum-tokens version bump). Use whenever asked to update, bump, or upgrade design tokens, or when told to run a token update.
How it works
- Mindset
- When to use
- Workflow
- Anti-patterns
SKILL.md preview
--- name: token-update description: Dispatches to the correct design token update workflow (custom tokens only vs @adobe/spectrum-tokens version bump). Use whenever asked to update, bump, or upgrade design tokens, or when told to run a token update. --- # Token update ## Mindset You are a dispatcher, not a workflow. The full steps for both paths already live in [gen2/packages/tools/swc-tokens/README.md](../../../gen2/packages/tools/swc-tokens/README.md#updating-tokens) — never re-derive, restate, or summarize those steps here. Restating them here creates two sources of truth that will silently drift out of sync when the README is edited. Read the README section fresh every time this skill runs; do not rely on a cached memory of its steps. ## When to use Any request shaped like "update the tokens," "bump `@adobe/spectrum-tokens`," "upgrade the token package," "I changed a custom token," or similar. This applies regardless of the current working directory — most requests will come from the repo root, but treat any location the same way. ## Workflow 1. Determine which path applies: - **Custom tokens only**: changes are confined to `gen2/packages/tools/swc-tokens/custom/` and there is no `@adobe/spectrum-tokens` version change. - **Package version bump**: `@adobe/spectrum-tokens` in `package.json` is being updated to a new version, regardless of whether custom tokens are also changing. - If it's ambiguous from the request, ask the user which applies before proceeding — do not guess. 2. Read [gen2/packages/tools/swc-tokens/README.md](../../../gen2/packages/tools/swc-tokens/README.md), starting at the `## Updating tokens` heading, and follow whichever of the two linked sections matches: - `## Upon Custom Token Data Update` - `## Upgrading @adobe/spectrum-tokens` 3. Execute that section's steps in the order given. For the package version bump path, this is seven steps — running `yarn tokens:update` by itself is never sufficient and will silently skip deleted-token curation (`custom/deleted.json`) and broken `token()` reference fixes in migrated CSS. ## Anti-patterns - Don't assume `yarn tokens:update` alone completes a `@adobe/spectrum-tokens` version bump. - Don't copy the step lists from the README into a plan or response — link to the section instead, so there is one canonical copy.
Versions
The database has no other skills named token-update.
Database snapshot: 13.11.2026 · package version bd4446acad0d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100design-data
Look up Spectrum design tokens, component schemas, and design-system decisions when building with or extending Adobe Spectrum. Use when the user asks about token values, component options, naming conventions, or wants to validate/explore design-token data. Also triggers when a… - 90tone-token
Design or refactor a design token architecture — naming, tiers, and coverage. Use when asked to "design a token architecture", "fix token naming", or "refactor our tokens". - 95spectrum-web-components
Build UIs with Spectrum Web Components (SWC), Adobe's Spectrum 1 web component library. Use when developers are working with @spectrum-web-components/* packages or sp-* custom elements. Includes component API references, usage examples, accessibility guidance, and integration guides. - 95spectrum-wc
Build UIs with Spectrum 2 Web Components (swc-* elements, @adobe/spectrum-wc). Use when developers are working with the @adobe/spectrum-wc package or swc-* custom elements. Includes component and pattern API references (properties, slots, events, CSS custom properties, CSS… - 100token-architecture
Use when building or restructuring design token systems — global tokens, semantic tokens, component tokens, naming conventions, theming, and multi-platform token distribution - 100design-tokens
Generate or improve a complete design token system covering color, typography, spacing, radius, shadows, and motion. Use when the user asks for design tokens, to generate tokens, or to build a token system.