design-tokens

Standardize UI design token usage and component styling for Keystone UI React components.

3|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/keystone-ui/react --skill design-tokens-keystone-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-tokens
Source: https://github.com/keystone-ui/react/tree/main/.claude/skills/design-tokens
Command: npx skills add https://github.com/keystone-ui/react --skill design-tokens-keystone-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents style drift in the Keystone UI React component library by defining the tokens, spacing, focus states, and component part conventions that every UI element should follow.

Core Features & Use Cases

  • Theme Token Guidance: Use consumer-owned CSS variables and semantic Tailwind classes for backgrounds, borders, rings, shadows, and text colors.
  • Component Consistency Rules: Apply shared conventions for radius, disabled states, popup patterns, icon sizing, transitions, and data-slot naming across components.
  • Use Case: When building or updating a button, input, select, or popup, this Skill helps you choose the right token, state, and class pattern so the component matches the rest of the library.

Quick Start

Apply the design-tokens skill whenever you create or edit a component in packages/ui/src/ so the implementation follows the library's established styling and theming rules.

Frequently Asked Questions about design-tokens

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

FAQPage Schema
How do I standardize UI design token usage and component styling in a React component library?

To standardize UI design token usage, apply consumer-owned CSS variables and semantic Tailwind classes for backgrounds, borders, rings, and shadows. This approach ensures every React component maintains visual consistency and preserves accessibility across the library.

What are design tokens and how do they prevent style drift in React component libraries?

Design tokens are standardized styling variables defining spacing, focus states, and component conventions. By enforcing shared rules for disabled states, popup patterns, and data-slot attributes, they prevent style drift and maintain visual consistency throughout the React component library.

How do I apply consistent focus rings and disabled states using Tailwind CSS?

Apply consistent focus rings and disabled states by using semantic Tailwind classes mapped to consumer-owned theme variables. Following shared component conventions for radius, rings, and transitions ensures accessibility and visual parity across all UI elements.

Does the design-tokens skill require specific dependencies to manage React component theming?

No specific dependencies are required. The design-tokens skill relies on consumer-owned CSS variables and semantic Tailwind classes to manage React component theming, ensuring components remain accessible and maintainable without external library dependencies.

When should I use data-slot attributes and popup patterns in a React component library?

Use data-slot attributes and popup patterns whenever creating or updating components in packages/ui/src/. Applying these shared conventions ensures that elements like inputs, selects, and popups match the library's established styling rules and maintain accessibility.