extract

Identify reusable UI patterns, components, and design tokens for consolidation into a design system.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/han-so1omon/ikam --skill extract-han-so1omon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/han-so1omon/ikam/tree/main/skills/extract
Command: npx skills add https://github.com/han-so1omon/ikam --skill extract-han-so1omon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract and consolidate reusable UI patterns, components, and design tokens into a scalable design system to improve consistency and reduce duplication.

Core Features & Use Cases

  • Identify reusable patterns, components, and tokens across a codebase.
  • Create a plan for extracting, tokenizing, and consolidating into a shared library.
  • Document and migrate existing UI pieces to the design system for broad reuse.

Quick Start

Analyze your design repository to identify repeating UI patterns and outline a plan to extract them into a cohesive design system.

Frequently Asked Questions about extract

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

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

Extracting design tokens involves identifying hard-coded values across your codebase and replacing them with a structured naming convention to ensure scalable and consistent UI styling.

What is the best way to extract design tokens from a component library?

Extracting design tokens involves identifying hard-coded values across your codebase and replacing them with a structured naming convention to ensure scalable and consistent UI styling.

How do I document a migration path for existing UI components?

Documenting a migration path requires outlining a structured extraction plan that maps existing duplicated UI pieces to the newly consolidated design system for broad reuse.

Can I use this to unify UI patterns across both web and mobile projects?

Yes, you can apply this extraction process to design codebases and component libraries across web and mobile projects where patterns are duplicated and tokens are hard-coded.

When do I need to tokenize hard-coded values in my codebase?

You need to tokenize hard-coded values when your codebase suffers from duplicated UI patterns, requiring a structured extraction plan and token naming conventions to form a cohesive design system.