extract

Extract reusable UI patterns, components, and design tokens from codebases.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Ikki-Group/erp --skill extract-ikki-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/Ikki-Group/erp/tree/main/.agents/skills/extract
Command: npx skills add https://github.com/Ikki-Group/erp --skill extract-ikki-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify repeated UI patterns, hard-coded values, and opportunities for tokens, then consolidate these findings into a cohesive design system to improve consistency and reduce duplication.

Core Features & Use Cases

  • Identify repeated components and UI patterns across projects.
  • Extract hard-coded values into design tokens and establish a token convention.
  • Plan migration to replace old implementations with shared components and tokens across codebases.

Quick Start

Identify a target area with reusable UI patterns and run the extraction plan to create shared 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 extract reusable UI patterns from my codebase?

To extract reusable UI patterns, identify repeated components across projects, plan the migration, and consolidate them into a shared design system to reduce duplication and improve consistency across apps.

What is the best way to consolidate hard-coded values into design tokens?

Consolidating hard-coded values into design tokens requires identifying repeated patterns in your codebase, establishing a token convention, and applying type-safe guidelines to standardize your multi-project UI libraries.

How do I plan a migration to replace old implementations with shared components?

Planning a migration to shared components involves discovering reusable UI patterns, extracting tokens, and enforcing clear guardrails to replace old implementations consistently across multiple codebases.

Can I use this to standardize a design system across multiple projects?

Yes, you can standardize a design system across multiple projects by identifying repeated UI components, extracting hard-coded values into tokens, and enforcing type-safe guidelines for consistency across apps.

Do I need existing design tokens to extract UI patterns?

No, you do not need existing design tokens; the extraction process identifies hard-coded values and repeated UI patterns first, then establishes a token convention to consolidate them into a cohesive design system.

When should I avoid extracting UI patterns into a design system?

You should avoid extracting UI patterns if your project lacks repeated components or multi-project UI libraries, as the process targets consistency across apps and requires clear migration guardrails to be effective.