ckm:design-system

Connect primitive design values to semantic and component tokens.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Postalocity/template-microsite --skill ckm-design-system-postalocity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ckm:design-system
Source: https://github.com/Postalocity/template-microsite/tree/main/.opencode/skills/ui-ux-pro-max--design-system
Command: npx skills add https://github.com/Postalocity/template-microsite --skill ckm-design-system-postalocity

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Token-driven design systems enable brand-consistent UI and scalable development by linking primitive values to semantic tokens and per-component configurations, ensuring a single source of truth across products and presentations.

Core Features & Use Cases

  • Token Architecture: three-layer structure (primitive → semantic → component) with CSS variables for spacing, typography, color, and radii.
  • Brand consistency and isolation: separate brand configurations and institutional knowledge bases to speed theming and reduce cross-brand leakage.
  • Slide and design tooling: templates, references, and integration patterns for design-to-code handoff, tokens-driven slides, and Tailwind integration.

Quick Start

Generate and apply a token-driven design system by initializing tokens, then rendering brand-consistent slides and UI with the provided templates.

Frequently Asked Questions about ckm:design-system

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

FAQPage Schema
How do I create a scalable design token architecture for multiple brands?

To create a scalable design token architecture, connect primitive design values to semantic and component tokens using CSS variables. This three-layer structure establishes a single source of truth for spacing, typography, color, and radii across multiple brands.

What is the best way to manage Tailwind integration with CSS variables?

Manage Tailwind integration by mapping design tokens to CSS variables within a three-layer architecture. This enforces token discipline and enables consistent, brand-aligned UI rendering by linking primitive values directly to component configurations.

How do I prevent style leakage when theming multiple brands?

Prevent style leakage by maintaining separate brand configurations within your design token system. This brand isolation approach ensures semantic and component tokens remain distinct for each brand, accelerating theming without cross-brand contamination.

Can I use design tokens to generate consistent slide templates?

Yes, you can use design tokens to generate consistent slide templates. The system provides slide-driven design workflows that leverage CSS variables and component tokens to enforce visual consistency and accelerate presentation work across brands.

Do I need a three-layer token structure for design-to-code handoff?

A three-layer token structure is recommended for reliable design-to-code handoff. Enforcing token discipline from primitive to component levels ensures semantic values translate accurately into code and maintain UI consistency across products.

Why does my design system lack consistency across different UI components?

Your design system lacks consistency because it likely bypasses component tokens. Linking semantic tokens to per-component configurations enforces a single source of truth, ensuring spacing, typography, and color remain uniform across all UI.