extract

Extract reusable design tokens and components from UI patterns.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/tanaka-mambinge/dotfiles --skill extract-tanaka-mambinge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/tanaka-mambinge/dotfiles/tree/main/ai-configs/skills/impeccable-extract
Command: npx skills add https://github.com/tanaka-mambinge/dotfiles --skill extract-tanaka-mambinge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and consolidates reusable UI patterns, components, and tokens into a unified design system to enable systematic reuse across products.

Core Features & Use Cases

  • Pattern discovery: Analyze UI for repeated components and tokens to identify extraction candidates.
  • Token creation: Convert hard-coded values into tokens with semantic naming.
  • Migration guidance: Provide steps to replace existing implementations with shared versions.
  • Documentation: Update design-system docs and usage examples.

Quick Start

Identify existing patterns in your UI codebase and start consolidating them into reusable components and tokens.

Frequently Asked Questions about extract

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

FAQPage Schema
How do I consolidate UI patterns into a reusable design system?

To consolidate UI patterns into a design system, analyze your codebase for repeated components and hard-coded values, then extract them into shared components and semantic design tokens for systematic reuse across products.

What are design tokens and when do I need to extract them?

Design tokens are semantic variables that replace hard-coded UI values. You need to extract them when repeated styling patterns cause fragmentation, ensuring visual consistency and easier maintenance across multiple projects.

How do I migrate existing components to a shared design system?

To migrate existing components to a shared design system, follow the provided migration steps to replace hard-coded implementations with shared versions, update naming conventions, and generate documentation with usage examples.

Can I use this to systematize a component library across multiple projects?

Yes, you can systematize a component library across multiple projects by identifying extraction candidates, creating tokens with semantic naming, and defining supported variants to promote consistency and efficiency.

What's the best way to discover reusable components in my UI codebase?

The best way to discover reusable components is performing pattern discovery, which analyzes your UI codebase to identify repeated elements and hard-coded values as candidates for extraction into a unified design system.