ckm:design-system

Manage design tokens and generate slides from component specifications.

2|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/moshi-azz/moshiClaw-panel --skill ckm-design-system-moshi-azz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ckm:design-system
Source: https://github.com/moshi-azz/moshiClaw-panel/tree/main/data/skills/design-system
Command: npx skills add https://github.com/moshi-azz/moshiClaw-panel --skill ckm-design-system-moshi-azz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires brand, ui-styling, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive toolset for managing design tokens, creating component specifications, and generating brand-compliant slides.

Core Features & Use Cases

  • Token Architecture: Define and maintain a token architecture with three layers (primitive, semantic, component).
  • Component Specifications: Specify the appearance and behavior of UI components in a consistent manner.
  • Slide Generation: Automatically generate slides for presentations using design tokens and component specifications.
  • Use Case: If you're working on a design system for a company and need to ensure consistency across your applications, this Skill can help you maintain and generate your design tokens, component specifications, and slides.

Quick Start

Generate design tokens using the design-system skill.

Frequently Asked Questions about ckm:design-system

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

FAQPage Schema
How do I generate slides from design tokens and component specifications?

To generate brand-compliant slides, you use design tokens and component specifications as inputs. The system automatically reads these definitions to create presentation slides that match your UI architecture and styling rules.

What is a three-layer design token architecture and how does it work?

A three-layer design token architecture organizes UI styling into primitive, semantic, and component tokens. This structure separates raw values from functional meanings and specific component rules to maintain brand consistency across applications.

How do I generate CSS variables from a design token system?

You generate CSS variables by processing your defined design tokens through the system. The token architecture automatically translates primitive, semantic, and component layer definitions into usable CSS variables for your UI components.

Do I need existing brand guidelines to create component specifications?

Yes, you need existing design tokens and brand guidelines to create accurate component specifications. The system relies on these inputs to ensure generated UI components and slides maintain strict brand compliance.

Can I maintain UI consistency across multiple applications using design tokens?

Yes, you can maintain UI consistency across multiple applications by defining a centralized design token architecture. The system uses these tokens to generate uniform component specifications and brand-compliant slides.

What are the limitations of generating slides without component specifications?

Generating slides without component specifications or design tokens results in inaccurate output. The system requires these definitions to properly apply token architecture, CSS variables, and brand compliance to the presentation.