claude-design-extract

Extract visual design tokens from source code into a structured DESIGN.md file.

2|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/erclx/aitk --skill claude-design-extract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-design-extract
Source: https://github.com/erclx/aitk/tree/main/claude/skills/claude-design-extract
Command: npx skills add https://github.com/erclx/aitk --skill claude-design-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aitk, jq.

What problem does it solve?

This skill solves the problem of design drift and documentation debt by automatically generating a standardized DESIGN.md file from existing project prose, UI components, and configuration files.

Core Features & Use Cases

  • Automated Extraction: Scans project files like CLAUDE.md, CSS/Tailwind configs, and UI components to identify visual intent.
  • Standardized Templating: Uses a canonical seed template to ensure design tokens are captured in a consistent, machine-readable format.
  • Visual Preview: Integrates with the aitk CLI to render an HTML/CSS preview of the extracted design system for immediate verification.

Quick Start

Ask the assistant to extract the design system from the current project to bootstrap the documentation.

Frequently Asked Questions about claude-design-extract

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

FAQPage Schema
How do I generate a design system from existing CSS and UI components?

Generating a design system from existing CSS and UI components involves scanning project files like Tailwind configs and stylesheets to extract visual design tokens. This skill produces a structured DESIGN.md file that codifies existing visual patterns into a standardized format.

What is design token documentation and how does it prevent design drift?

Design token documentation captures visual intent like colors and typography in a machine-readable format. Automatically generating a DESIGN.md file from project source code prevents design drift and reduces documentation debt by codifying existing visual patterns consistently.

Do I need to install jq and aitk CLI to extract design tokens from source code?

Yes, extracting design tokens from source code requires installing both the aitk CLI and jq. These dependencies parse project signals and render the final HTML/CSS design preview for immediate verification of the extracted design system.

Can I bootstrap documentation from Tailwind configs and project prose?

Yes, you can bootstrap documentation from Tailwind configs and project prose. The skill scans files like CLAUDE.md, CSS configurations, and UI components to identify visual intent and generates a standardized DESIGN.md file using a canonical seed template.

What's the best way to visualize extracted design tokens for verification?

The best way to visualize extracted design tokens is by rendering an HTML/CSS preview. This skill integrates with the aitk CLI to render an immediate visual preview of the extracted design system, allowing you to verify the captured tokens directly.

What are the limitations of automated design system extraction from code?

Automated design system extraction from code relies on parsing existing files like stylesheets and UI components, so it cannot capture implicit design decisions not present in the source. It requires structured project files and the aitk CLI to parse signals and render previews.