ckm:design-system

Generate brand-compliant slide decks from token-driven design systems.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/jc180105/.opencode --skill ckm-design-system-jc180105
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ckm:design-system
Source: https://github.com/jc180105/.opencode/tree/main/.opencode/skills/design-design-system
Command: npx skills add https://github.com/jc180105/.opencode --skill ckm-design-system-jc180105

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Token-driven design systems and brand-aligned slide decks require a cohesive token architecture, semantic layers, and repeatable templates. This Skill provides token design, component specs, and slide-generation tooling to unify design language across products and presentations.

Core Features & Use Cases

  • Token architecture with three-layer tokens (primitive → semantic → component), CSS variables, and scalable spacing/typography scales.
  • Component specs and slide-generation system for brand-compliant presentations.
  • Use cases include design-token creation, design-system governance, and rapid slide deck production.

Quick Start

Run the provided tooling to generate tokens and slides for your brand deck.

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 brand-compliant slides using a design token architecture?

You generate brand-compliant slides by applying a three-layer token architecture—primitive, semantic, and component tokens—through provided slide-generation tooling. This ensures consistent design language across presentations and scalable design-to-code handoff.

What is a three-layer design token system and when do I need it for slide generation?

A three-layer design token system maps primitive values to semantic and component tokens. You need it when building scalable brand guidelines and repeatable slide templates to maintain visual consistency across products and decks.

How do I create CSS variables and spacing scales for design system governance?

Create CSS variables and spacing scales by defining primitive tokens, mapping them to semantic layers, and applying them to component specs. This Skill provides scripts and references to align tokens with design standards and governance.

Can I use this design token system for rapid slide deck production without external dependencies?

Yes, you can produce rapid slide decks without external dependencies. The Skill includes standalone scripts and references to run token generation and slide-pattern tooling directly for your brand-aligned presentations.

Does this design token architecture support design-to-code handoff for component specs?

Yes, the design token architecture supports design-to-code handoff by maintaining alignment between component specs and design standards. It applies semantic and component tokens to ensure scalable and repeatable template generation.

What are the limitations of using CSS variables for design tokens in brand guideline automation?

Using CSS variables for design tokens requires maintaining strict governance to prevent token drift across primitive and semantic layers. You must ensure component specs stay aligned with the design system to avoid inconsistent slide generation.