ckm:design-system

Establish a three-layer token architecture with CSS variables for theming.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/akshh229/Twin-Titans_Lazarus --skill ckm-design-system-akshh229
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ckm:design-system
Source: https://github.com/akshh229/Twin-Titans_Lazarus/tree/main/.codex/skills/design-system
Command: npx skills add https://github.com/akshh229/Twin-Titans_Lazarus --skill ckm-design-system-akshh229

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Token architecture and component specs unify design tokens, UI components, and slide templates across projects, enabling consistent theming and faster collaboration.

Core Features & Use Cases

  • Three-layer token model (primitive → semantic → component) with CSS variables for scalable theming.
  • Component specifications and slide templates to accelerate brand-aligned design-to-delivery workflows.
  • Reusable references and assets that support token generation, validation, and documentation.

Quick Start

Generate the token system artifacts by running the token generation scripts and assemble the design assets for your project.

Frequently Asked Questions about ckm:design-system

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

FAQPage Schema
How do I structure design tokens for scalable theming across multiple products?

Structure design tokens using a three-layer architecture: primitive, semantic, and component layers. This model unifies tokens and UI components with CSS variables, enabling consistent brand theming and scalable collaboration across multiple products.

What is a three-layer token architecture in a design system?

A three-layer token architecture maps primitive tokens to semantic tokens, which then map to component tokens. This hierarchy separates raw values from contextual meaning and UI component specs, allowing design teams to update themes without breaking underlying variables.

How do I generate design system artifacts and CSS variables for my project?

Generate design system artifacts by running the provided token generation scripts. These scripts process your three-layer token model and assemble reusable references, CSS variables, and design assets for immediate project integration.

Can I use CSS variables to manage component specs and slide templates?

Yes, CSS variables manage component specs and slide templates within this system. It provides reusable references and assets that support token validation and documentation, accelerating brand-aligned design-to-delivery workflows.

Does this token architecture workflow support frontend engineers and product managers?

Yes, the token architecture explicitly targets design teams, frontend engineers, and product managers. It satisfies requirements for three-layer token references, CSS variable usage, documentation, and tooling for generation and validation across brands.

What's the best way to document component specifications and design tokens?

Document component specifications by assembling design assets through the generation scripts. This establishes a unified documentation system that validates tokens and aligns slide templates with your component specs for consistent delivery.