extract

Identify and consolidate reusable UI components and design tokens into a design system.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/jatwell93/pharmacy-heatmap --skill extract-jatwell93
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/jatwell93/pharmacy-heatmap/tree/main/.agents/skills/extract
Command: npx skills add https://github.com/jatwell93/pharmacy-heatmap --skill extract-jatwell93

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.

Core Features & Use Cases

  • Pattern discovery: identify reusable UI components and tokens across a codebase, surface inconsistencies, and suggest standardizations.
  • Extraction planning: define which components and tokens to extract, establish naming conventions, variants, and migration steps.
  • System enrichment: generate or update a centralized design system, document usage guidelines, and support scalable refactors.

Quick Start

Identify opportunities to extract reusable patterns and tokens, and consolidate them into the design system.

Frequently Asked Questions about extract

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

FAQPage Schema
How do I extract reusable UI patterns and design tokens from an existing codebase?

To extract reusable UI patterns and design tokens, you analyze the codebase to identify repeated components, surface inconsistencies, and consolidate them into a coherent design system with standard naming conventions and systematic reuse guidelines.

What is design token extraction and when do I need it for my UI project?

Design token extraction identifies reusable visual values across multiple pages or apps. You need it when building a design system, refactoring repeated UI patterns, or standardizing components to enable systematic reuse and scalable refactors.

What's the best way to consolidate repeated components into a centralized design system?

The best way to consolidate repeated components is to perform pattern discovery, define extraction plans for variants, establish migration steps, and generate a centralized design system with documentation updates and usage guidelines.

Does design system extraction work for refactoring UI patterns across multiple apps?

Yes, design system extraction applies to UI projects requiring pattern discovery and component systemization across multiple pages or apps. It defines migration steps and documentation updates to support scalable refactors and systematic reuse.

How do I plan a migration to standardize UI components and establish naming conventions?

To plan a migration, you define which components and tokens to extract, establish naming conventions, set variants, and outline migration steps to update your design system documentation and support systematic reuse across refactored apps.