ui-tokens

Inspect and synchronize design tokens across JSON sources and CSS themes.

25|6|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/KRISHNA0R/PORTFOLIOv2 --skill ui-tokens-krishna0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-tokens
Source: https://github.com/KRISHNA0R/PORTFOLIOv2/tree/main/.agents/skills/ui-tokens
Command: npx skills add https://github.com/KRISHNA0R/PORTFOLIOv2 --skill ui-tokens-krishna0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Token drift occurs when the source of truth for tokens in JSON files diverges from CSS variables and theme wiring, causing UI inconsistencies and maintenance overhead.

Core Features & Use Cases

  • Inspect current token sets across JSON and CSS to identify drift and ensure alignment.
  • Add new tokens and wire them through both the JSON sources and the CSS implementations.
  • Update existing tokens and propagate changes to downstream components, themes, and styles.
  • Support dark-mode variants and semantic naming to ensure accessibility and consistency.

Quick Start

List tokens, add a new token, and propagate changes to align JSON and CSS across the design system.

Frequently Asked Questions about ui-tokens

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

FAQPage Schema
What causes design token drift between JSON and CSS variables?

Design token drift happens when JSON source files and CSS variable implementations diverge during updates, causing UI inconsistencies. Synchronizing tokens across both sources prevents this drift and ensures downstream components stay aligned.

How do I add a new design token and wire it through JSON and CSS?

To add a new design token, define it in the JSON source and wire it through the CSS variable implementation. Propagating changes across both files ensures downstream themes and components remain synchronized with the updated token.

Can I use this to enforce semantic naming and dark-mode support for CSS variables?

Yes, synchronizing design tokens enforces semantic naming conventions and supports dark-mode variants across JSON and CSS files. This ensures accessibility and consistent theme implementation throughout the design system.

Does this design token synchronization work with the StyleSeed Toss seed?

Yes, token synchronization is built for teams using the StyleSeed Toss seed with JSON token files and CSS variable implementations. It inspects and aligns tokens across these specific sources to prevent drift.

What is the best way to inspect existing design tokens for inconsistencies?

Inspecting current token sets across JSON sources and CSS themes is the best way to identify drift and ensure alignment. This process checks for inconsistencies between the declared JSON tokens and their CSS variable counterparts.

Why are my CSS variables out of sync with JSON design tokens?

CSS variables fall out of sync with JSON design tokens when updates are applied to one source without propagating to the other. Synchronizing design tokens across both JSON and CSS prevents this divergence and maintenance overhead.