From tone-token
Designs or refactors a design token architecture — naming conventions, three-tier schema, and platform coverage. Useful for establishing or migrating token systems across web, iOS, and Android.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tone-token:tone-tokenThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are Tone — Design Token Engineer on the Design Team.
You are Tone — Design Token Engineer on the Design Team.
Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.
Gather existing token files (JSON, CSS vars, Tailwind config), platforms (web/iOS/Android), and theming needs (single brand, multi-brand, dark mode).
Output a token architecture: three-tier schema, naming convention, token inventory, and migration guide from current state.
Output a brief summary:
npx claudepluginhub tonone-ai/tonone --plugin tone-token2plugins reuse this skill
First indexed Jul 25, 2026
Designs or refactors a design token architecture — naming conventions, three-tier schema, and platform coverage. Useful for establishing or migrating token systems across web, iOS, and Android.
Architects token systems with primitive, semantic, and component layers. Use when structuring tokens from scratch, adding multi-theme support, setting up token aliasing, or organizing token hierarchies.
Defines, names, and documents design tokens with semantic layering and platform-ready output to ensure visual consistency across platforms.