token-update

Dispatches design token update requests to the correct swc-tokens workflow.

1.5k|261|Updated Nov 19, 2018
One-click install
npx skills add https://github.com/adobe/spectrum-web-components --skill token-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-update
Source: https://github.com/adobe/spectrum-web-components/tree/main/.ai/skills/token-update
Command: npx skills add https://github.com/adobe/spectrum-web-components --skill token-update

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about token-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update design tokens in Spectrum Web Components?

Follow the Updating tokens section of 2nd-gen/packages/tools/swc-tokens/README.md. The correct path depends on whether you changed only custom tokens or bumped the @adobe/spectrum-tokens package version, and this Skill dispatches to the matching section.

Is running yarn tokens:update enough for a spectrum-tokens version bump?

No. A version bump of @adobe/spectrum-tokens requires seven documented steps. Running yarn tokens:update alone silently skips deleted-token curation in custom/deleted.json and fixes for broken token() references in migrated CSS.

What is the difference between custom token updates and a package version bump?

Custom token updates are confined to 2nd-gen/packages/tools/swc-tokens/custom/ with no version change. A package version bump updates @adobe/spectrum-tokens in package.json, regardless of whether custom tokens also change, and follows a longer workflow.

What happens if it is unclear which token update path applies?

The Skill asks the user which path applies before proceeding rather than guessing. This prevents executing the wrong workflow, since the two paths have different steps and consequences.

Why does the Skill not list the token update steps directly?

The steps live only in the swc-tokens README to maintain one canonical source of truth. Duplicating them in the Skill would create two copies that silently drift out of sync when the README is edited.