ckm:design-system

Organizes design tokens and component specs into scalable frameworks for brand-consistent slides.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tarang-tj/syllabus-ai --skill ckm-design-system-tarang-tj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ckm:design-system
Source: https://github.com/tarang-tj/syllabus-ai/tree/main/.claude/skills/design-system
Command: npx skills add https://github.com/tarang-tj/syllabus-ai --skill ckm-design-system-tarang-tj

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Token architecture and design-system specs are organized into a reusable framework enabling brand-aligned slides and design handoffs, reducing duplication and inconsistencies.

Core Features & Use Cases

  • Token architecture: primitive → semantic → component layers that enable consistent theming and design-to-code handoff.
  • Slide-generation templates: brand-compliant slide scaffolds and example patterns for marketing, product, and design decks.
  • References and tooling: a curated set of references, scripts, and starter templates to accelerate design-system adoption.

Quick Start

Use this skill to bootstrap a token-driven design system that outputs brand-consistent slides and components.

Frequently Asked Questions about ckm:design-system

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

FAQPage Schema
How do I scale design tokens into slide-ready components for brand-consistent presentations?

To scale design tokens into slide-ready components, you map primitive tokens to semantic and component layers, applying CSS variables to enforce brand consistency across all generated slide scaffolds and marketing decks. This reduces design duplication and inconsistencies.

What is the three-layer token architecture for design systems?

The three-layer token architecture organizes design tokens into primitive, semantic, and component layers. This structure enables consistent theming and streamlines design-to-code handoffs by mapping raw values to contextual meanings before applying them to specific UI elements.

How do I enforce CSS variable usage across a branding initiative?

You enforce CSS variable usage by structuring your design system framework to require token-driven styling for all outputs. The system applies semantic mapping to generate brand-compliant slide scaffolds, ensuring variables are consistently utilized across component specs.

Can I use this design system framework for marketing, product, and design decks?

Yes, the framework provides brand-compliant slide-generation templates specifically tailored for marketing, product, and design decks. It uses starter templates and references to accelerate design-system adoption across various presentation contexts.

Do I need existing component specs to bootstrap a token-driven design system?

No, you do not need existing component specs to start. You can use the provided references, scripts, and starter templates to bootstrap a token-driven design system from scratch, organizing token architecture into a reusable framework for design handoffs.

What's the best way to organize design tokens for design-to-code handoffs?

The best way to organize design tokens for handoffs is implementing a three-layer architecture that progresses from primitive to semantic to component tokens. This scalable design system framework ensures brand-aligned outputs and reduces inconsistencies during slide generation.