ckm:design-system

nextlevelbuilder/ui-ux-pro-max-skill · updated May 4, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/nextlevelbuilder/ui-ux-pro-max-skill --skill ckm:design-system
0 commentsdiscussion
summary

Token architecture, component specifications, systematic design, slide generation.

skill.md

Design System

Token architecture, component specifications, systematic design, slide generation.

When to Use

  • Design token creation
  • Component state definitions
  • CSS variable systems
  • Spacing/typography scales
  • Design-to-code handoff
  • Tailwind theme configuration
  • Slide/presentation generation

Token Architecture

Load: references/token-architecture.md

Three-Layer Structure

Primitive (raw values)
Semantic (purpose aliases)
Component (component-specific)

Example:

/* Primitive */
--color-blue-600: #2563EB;

/* Semantic */
--color-primary: var(--color-blue-600);

/* Component */
--button-bg: var(--color-primary);

Quick Start

Generate tokens:

node scripts/generate-tokens.cjs --config tokens.json -o tokens.css

Validate usage:

node scripts/validate-tokens.cjs --dir src/

References

Topic File
Token Architecture references/token-architecture.md
Primitive Tokens references/primitive-tokens.md
Semantic Tokens references/semantic-tokens.md
Component Tokens references/component-tokens.md
Component Specs references/component-specs.md
States & Variants references/states-and-variants.md
Tailwind Integration references/tailwind-integration.md

Component Spec Pattern

Property Default Hover Active Disabled
Background primary primary-dark primary-darker muted
Text white white white muted-fg
Border none none none muted-border
Shadow sm md none none

Scripts

Script Purpose
generate-tokens.cjs Generate CSS from JSON token config
validate-tokens.cjs Check for hardcoded values in code
search-slides.py BM25 search + contextual recommendations
slide-token-validator.py Validate slide HTML for token compliance
fetch-background.py Fetch images from Pexels/Unsplash

Templates

Template Purpose
design-tokens-starter.json Starter JSON with three-layer structure

Integration

With brand: Extract primitives from brand colors/typography With ui-styling: Component tokens → Tailwind config

Skill Dependencies: brand, ui-styling Primary Agents: ui-ux-designer, frontend-developer

Slide System

Brand-compliant presentations using design tokens + Chart.js + contextual decision system.

Source of Truth

File Purpose
docs/brand-guidelines.md Brand identity, voice, colors
assets/design-tokens.json Token definitions (primitive→semantic→component)
assets/design-tokens.css CSS variables (import in slides)
assets/css/slide-animations.css CSS animation library

Slide Search (BM25)

# Basic search (auto-detect domain)
python scripts/search-slides.py "investor pitch"

# Domain-specific search
python scripts/search-slides.py "problem agitation" -d copy
python scripts/search-slides.py "revenue growth" -d chart

# Contextual search (Premium System)
python scripts/search-slides.py "problem slide" --context --position 2 --total 9
python scripts/search-slides.py "cta" --context --position 9 --prev-emotion frustration

Decision System CSVs

File Purpose
data/slide-strategies.csv 15 deck structures + emotion arcs + sparkline beats
data/slide-layouts.csv 25 layouts + component variants + animations
data/slide-layout-logic.csv Goal → Layout + break_pattern flag
data/slide-typography.csv Content type → Typography scale
data/slide-color-logic.csv Emotion → Color treatment
data/slide-backgrounds.csv Slide type → Image category (Pexels/Unsplash)
data/slide-copy.csv 25 copywriting formulas (PAS, AIDA, FAB)
data/slide-charts.csv 25 chart types with Chart.js config

Contextual Decision Flow

1. Parse goal/context
2. Search slide-strategies.csv → Get strategy + emotion beats
3. For each slide:
   a. Query slide-layout-logic.csv → layout + break_pattern
   b. Query slide-typography.csv → type scale
   c. Query slide-color-logic.csv → color treatment
   d. Query slide-backgrounds.csv → image if needed
   e. Apply animation class from slide-animations.css
4. Generate HTML with design tokens
5. Validate with slide-token-validator.py

Pattern Breaking (Duarte Sparkline)

Premium decks alternate between emotions for engagement:

"What Is" (frustration) ↔ "What Could Be" (hope)

System calculates pattern breaks at 1/3 and 2/3 positions.

Slide Requirements

ALL slides MUST:

  1. Import assets/design-tokens.css - single source of truth
  2. Use CSS variables: var(--color-primary), var(--slide-bg), etc.
  3. Use Chart.js for charts (NOT CSS-only bars)
  4. Include navigation (keyboard arrows, click, progress bar)
  5. Center align content
  6. Focus on persuasion/conversion

Chart.js Integration

<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/chart.umd.min.js"></script>

<canvas id="revenueChart"></canvas>
<script>
new Chart(document.getElementById('revenueChart'), {
    type: 'line',
    data: {
        labels: ['Sep', 'Oct', 'Nov', 'Dec'],
        datasets: [{
            data: [5, 12, 28, 45],
            borderColor: '#FF6B6B',  // Use brand coral
            backgroundColor: 'rgba(255, 107, 107, 0.1)',
            fill: true,
            tension: 0.4
        }]
    }
});
</script>

Token Compliance

/* CORRECT - uses token */
background: var(--slide-bg);
color: var(--color-primary);
font-family: var(--typography-font-heading);

/* WRONG - hardcoded */
background: #0D0D0D;
color: #FF6B6B;
font-family: 'Space Grotesk';

Reference Implementation

Working example with all features:

assets/designs/slides/claudekit-pitch-251223.html

Command

/slides:create "10-slide investor pitch for ClaudeKit Marketing"

Best Practices

  1. Never use raw hex in components - always reference tokens
  2. Semantic layer enables theme switching (light/dark)
  3. Component tokens enable per-component customization
  4. Use HSL format for opacity control
  5. Document every token's purpose
  6. Slides must import design-tokens.css and use var() exclusively
how to use ckm:design-system

How to use ckm:design-system on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add ckm:design-system
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/nextlevelbuilder/ui-ux-pro-max-skill --skill ckm:design-system

The skills CLI fetches ckm:design-system from GitHub repository nextlevelbuilder/ui-ux-pro-max-skill and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/ckm:design-system

Reload or restart Cursor to activate ckm:design-system. Access the skill through slash commands (e.g., /ckm:design-system) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.758 reviews
  • Luis Ramirez· Dec 24, 2024

    ckm:design-system is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Carlos Nasser· Dec 24, 2024

    Solid pick for teams standardizing on skills: ckm:design-system is focused, and the summary matches what you get after install.

  • Chaitanya Patil· Dec 20, 2024

    ckm:design-system fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Noor Perez· Dec 12, 2024

    We added ckm:design-system from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Nia Perez· Dec 4, 2024

    Keeps context tight: ckm:design-system is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Camila Rao· Nov 23, 2024

    ckm:design-system has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Diego Liu· Nov 19, 2024

    I recommend ckm:design-system for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sofia Ghosh· Nov 15, 2024

    Solid pick for teams standardizing on skills: ckm:design-system is focused, and the summary matches what you get after install.

  • Nikhil Park· Nov 15, 2024

    ckm:design-system is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Piyush G· Nov 11, 2024

    Registry listing for ckm:design-system matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 58

1 / 6