cc-figma-tokens

To sync design system tokens to Figma, this skill automates the creation and maintenance of Figma token libraries from component-contracts token files. It reads your project configuration, builds an in-memory token map, and updates Figma collections when primitives or semantics change.

Yes, creating semantic and primitive token collections in Figma from code is the core function. This skill generates two Figma collections with value-based primitive tokens and alias-based semantic tokens that components bind to, using CSS-like var() syntax for alias relationships.

Maintaining Figma variables for a design system is best handled by automating token library creation from component-contracts. This skill validates token directories before writes, builds an in-memory token map, and establishes proper scopes and alias relationships for native Figma variables.

Yes, you need a .component-contracts configuration file to generate Figma token libraries. This skill reads project-wide configuration from this file and validates token directories before executing any Figma writes, ensuring a safe and consistent setup.

Semantic token alias updates in Figma require building an in-memory token map before any use_figma calls. This skill ensures proper scopes and CSS-like var() syntax are applied, creating correct alias relationships between your primitive and semantic collections.

Yes, cc-figma-tokens requires and encourages the use of figma-use and figma-generate-library skills. It mandates passing skillNames: "cc-figma-tokens" for all use_figma calls to ensure proper integration when syncing token definitions to Figma.