ckm-design-system

Generates three-layer design tokens, component specifications, and brand-compliant HTML slide decks.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill ckm-design-system-aicodepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ckm-design-system
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/ckm-design-system
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill ckm-design-system-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Maintaining visual consistency across components and presentations is hard when colors, spacing, and typography are hardcoded everywhere. This Skill establishes a single source of truth through a three-layer token architecture (primitive, semantic, component) and enforces it with automated validation, while also generating brand-compliant slide decks. ## Core Features & Use Cases - Design Token Generation: Convert JSON token configs into CSS variables or Tailwind theme config with automatic reference resolution and dark-mode support. - Token Compliance Validation: Scan HTML and source code for hardcoded hex colors, rgb values, and fonts that bypass the token system. - Slide Deck Generation: Create persuasive HTML presentations using decision-system CSVs (layouts, typography, color logic, copywriting formulas), Chart.js charts, BM25 slide search, and curated Pexels backgrounds. - Use Case: A frontend developer needs a consistent button system and an investor pitch deck. They generate tokens from the starter JSON, validate their components against the tokens, then produce a 10-slide deck that imports design-tokens.css and passes the token validator. ## Quick Start Ask the assistant to generate design tokens from the starter JSON config and then create a brand-compliant pitch deck using the slide generation scripts.

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 CSS variables from a design tokens JSON file?

Run the generate-tokens.cjs script with your JSON config: node generate-tokens.cjs --config tokens.json -o tokens.css. It resolves token references like {primitive.color.blue.600} and outputs primitive, semantic, and component layers, plus a dark-mode block. A --format tailwind option emits Tailwind theme colors instead.

How do I check HTML files for hardcoded colors instead of design tokens?

Use the html-token-validator.py script to scan slides and infographics for hex, rgb, and hsl values outside var() references. It verifies the design-tokens.css import exists and allows brand-color rgba values needed for transparency effects. Run it with --type slides or point it at a specific file.

What is the three-layer design token architecture?

It separates raw primitive values (hex colors, spacing) from semantic aliases (primary, muted) and component-specific tokens (button-bg). Components reference only component tokens, which reference semantic tokens, enabling theme switching by redefining the semantic layer.

Does the slide generator support charts and dark themes?

Yes, slides integrate Chart.js 4 for data visualization and the token system includes a dark semantic layer for theme switching. All slides must import design-tokens.css and use var() references exclusively, which the validator enforces.

What are the limitations of the CSS-only slide generation approach?

The generate-slide.py script produces static HTML decks with a fixed set of slide types (title, problem, solution, metrics, chart, testimonial, CTA). Complex layouts beyond these templates require manual HTML authoring, and charts in generated decks should use Chart.js rather than CSS-only bars for production use.