extract

Extract reusable UI components, design tokens, and layout patterns into a design system.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/yahya-azeem/Pokedex --skill extract-yahya-azeem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/yahya-azeem/Pokedex/tree/main/library/impeccable/skills/extract
Command: npx skills add https://github.com/yahya-azeem/Pokedex --skill extract-yahya-azeem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify and consolidate repeated UI patterns, reusable components, and hard-coded styling values into a maintainable design system instead of letting duplicates and inconsistencies grow over time.

Core Features & Use Cases

  • Pattern detection: Finds repeated components, inconsistent variations, and general layout/composition patterns worth systematizing.
  • Design-token extraction: Converts hard-coded colors, spacing, typography, and other values into a clear token hierarchy (primitive vs semantic) with documented usage.
  • Component and migration workflow: Creates reusable components with accessible props APIs and variants, then migrates existing usages to the shared versions and updates documentation (e.g., component catalogs or Storybook).

Quick Start

Use the extract skill to analyze your UI directory for repeated components and hard-coded styling values and propose a targeted extraction plan.

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 components from duplicated code?

To extract design tokens from hard-coded styling values, this Skill detects repeated colors, spacing, and typography in your UI, normalizes them into a documented primitive vs semantic token hierarchy, and replaces existing usages with the shared tokens.

What is the process for refactoring repeated UI patterns into a design system?

Refactoring repeated UI patterns involves analyzing your design system structure, selecting extraction candidates by reuse value, generating type-safe component APIs, migrating existing usages to shared versions, and updating component documentation like Storybook catalogs.

Can I use this to document design tokens and component conventions?

Yes, you can use this Skill to document design tokens and component conventions. It updates your design system documentation by generating token usage guidelines and accessible prop API definitions during the component extraction and migration workflow.

What's the best way to consolidate inconsistent UI variations into a shared component library?

The best way to consolidate inconsistent UI variations is to detect repeated components, normalize hard-coded styling values into design tokens, create reusable components with accessible variants, and migrate existing usages to the shared library.

Does extracting UI components require an existing design system structure to work?

Extracting UI components requires an existing UI directory to analyze for repeated patterns and hard-coded styling values. The Skill evaluates your current design system structure to propose a targeted extraction plan based on component reuse value.