Qdesign

Generate DESIGN.md design token specifications from codebases and Tailwind configurations.

6|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/inho-team/qe-framework --skill qdesign
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Qdesign
Source: https://github.com/inho-team/qe-framework/tree/main/skills/Qdesign
Command: npx skills add https://github.com/inho-team/qe-framework --skill qdesign

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams and frontend projects often lack a single source of truth for tokens, typography, spacing, and guidelines, leading drift between design and implementation. This skill automates the creation and synchronization of DESIGN.md from live tokens and reference material.

Core Features & Use Cases

  • Automatically generate DESIGN.md as the canonical design-system specification for a project.
  • Extract tokens (colors, typography, spacing, motion) from codebases and design references to bootstrap a complete document.
  • Support live scanning (--scan) to bootstrap tokens from tailwind/theme configs and tailor DESIGN.md for the project.
  • Validate and align with design tooling (e.g., Qdesign validators) to ensure token coherence across Tailwind configs and components.

Quick Start

Run the Qdesign skill to generate DESIGN.md from your project tokens and references.

Frequently Asked Questions about Qdesign

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

FAQPage Schema
How do I generate a design system specification from existing tokens?

To generate a design system specification from existing tokens, the Skill automatically scans your codebase and Tailwind configurations to extract typography, spacing, and color tokens, bootstrapping a complete canonical document. It uses live scanning to synchronize live theme configurations into a single source of truth.

How do I extract design tokens from a Tailwind configuration file?

You can extract design tokens from a Tailwind configuration file by running a live scan. The Skill parses your theme configurations to automatically identify and pull colors, typography, spacing, and motion tokens to bootstrap a complete tokenized specification document.

What is the best way to enforce OKLCH color tokens and dark-mode mappings?

The best way to enforce OKLCH color tokens and dark-mode mappings is to use an automated validation skill that checks contrast requirements and cross-project consistency. It validates extracted tokens against design tooling to ensure coherent dark-mode mappings and color specifications.

Can I bootstrap a design doc from code without manual token documentation?

Yes, you can bootstrap a design doc directly from code without manual token documentation. The Skill automatically extracts tokens from your live codebases, Tailwind theme configs, and design references to generate a complete DESIGN.md file as the single source of truth.

Why does my frontend design drift from the original implementation guidelines?

Frontend design drifts from original implementation guidelines when projects lack a single source of truth for tokens and typography. Automatically generating and synchronizing a canonical specification from live tokens and reference material prevents this drift and ensures cross-project consistency.

Does this design token validation approach work with existing Tailwind configs?

Yes, this design token validation approach works with existing Tailwind configs. The Skill aligns with design tooling validators to ensure token coherence across your Tailwind configurations and components, validating extracted tokens for cross-project consistency.