design-system

Translate design specifications into structured CSS variables and Tailwind tokens.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/Posteriot/makalah-app --skill design-system-posteriot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/Posteriot/makalah-app/tree/main/.agent/skills/design-system
Command: npx skills add https://github.com/Posteriot/makalah-app --skill design-system-posteriot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the manual effort of translating Figma or design documents into consistent design tokens so that styling remains scalable and theme-ready across the app.

Core Features & Use Cases

  • Token Extraction: Identify primitives such as hex colors, spacing, and typography values, then organize them into semantic roles like bg-primary or text-success.
  • Implementation Guidance: Define CSS variables in :root and extend tailwind.config.js so tokens can be consumed via utility classes and global styling hooks.
  • Verification & Use Case: Validate WCAG-friendly contrast and confirm that changing a primitive (e.g., a brand color) cascades to semantic tokens, ensuring consistent theming in light/dark mode builds.

Quick Start

Convert the provided layout and color specs into CSS variables and Tailwind tokens.

Frequently Asked Questions about design-system

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

FAQPage Schema
How do I translate Figma design specs into CSS variables and Tailwind tokens?

To translate Figma specs into CSS variables and Tailwind tokens, extract primitive values like hex colors and spacing, then map them to semantic roles such as bg-primary. You define these tokens in the :root selector and extend the tailwind.config.js file for utility class consumption.

What are design tokens and when do I need them for responsive theming?

Design tokens are structured variables representing visual design primitives like color and spacing. You need them for responsive theming to maintain component styling consistency across light and dark modes, ensuring that updating a single primitive cascades changes to all semantic token references.

How do I structure a typography scale and spacing system for design tokens?

Structure a typography scale and spacing system by extracting primitive values from design documents and assigning them intuitive naming conventions. These values are then documented as CSS variables and integrated into the Tailwind configuration to provide consistent, theme-ready styling hooks across the application.

Can I use design tokens to verify WCAG-friendly contrast for light and dark mode?

Yes, you can use design tokens to verify WCAG-friendly contrast. By organizing colors into semantic roles and validating their relationships, changing a base primitive automatically cascades to semantic tokens, which helps confirm that both light and dark mode builds maintain accessible contrast ratios.

Does this token extraction approach work without manual CSS variable mapping?

Yes, this approach removes the manual effort of translating design documents into CSS variables. It automatically identifies primitives like hex colors and typography values, then organizes them into semantic roles to keep styling scalable and theme-ready across your product without direct manual mapping.