tokens

Govern design systems through token hierarchy, documentation standards, and semantic versioning.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Objective-Arts/lens-dist --skill tokens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tokens
Source: https://github.com/Objective-Arts/lens-dist/tree/main/canon/tokens
Command: npx skills add https://github.com/Objective-Arts/lens-dist --skill tokens

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need for robust governance in design systems, ensuring consistency, maintainability, and clear communication through documentation, versioning, and token management.

Core Features & Use Cases

  • Design Token Management: Defines a clear hierarchy (Global, Semantic, Component) and categories for design tokens (color, spacing, typography, etc.), ensuring a unified visual language.
  • Component Documentation Standards: Outlines a comprehensive structure for documenting individual components, including usage, variants, props, states, accessibility, and changelogs.
  • Versioning and Deprecation: Establishes clear guidelines for semantic versioning and a phased deprecation process for components and tokens to manage breaking changes effectively.
  • Use Case: A team can use this Skill to define and enforce standards for their design system, ensuring all new components and tokens are properly documented, versioned, and integrated, preventing design and development inconsistencies.

Quick Start

Use the tokens skill to document the new 'Avatar' component according to the defined standards.

Frequently Asked Questions about tokens

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

FAQPage Schema
What is design system governance and why is it needed?

Design system governance establishes structured documentation, versioning, and token management to ensure consistency, maintainability, and clear communication across a scalable design system.

How do I structure design token hierarchy for a component library?

Structure design tokens by enforcing a clear hierarchy of Global, Semantic, and Component levels, categorizing them by attributes like color, spacing, and typography for a unified visual language.

What should be included in component documentation standards?

Component documentation standards must outline comprehensive structures including usage guidelines, variants, props, states, accessibility requirements, and changelogs for each individual component.

How do I manage semantic versioning and deprecation for design tokens?

Manage breaking changes by establishing clear guidelines for semantic versioning and a phased deprecation process for components and tokens, treating the design system as a defined product.

Can I use this to enforce contribution workflows for a design system?

Yes, you can define and enforce standards for your design system, ensuring all new components and tokens are properly documented, versioned, and integrated through defined release and contribution workflows.

What is the best way to document a new component according to design system standards?

The best way to document a new component is to follow defined governance standards, capturing its usage, variants, props, states, accessibility, and changelog to prevent design and development inconsistencies.