extract

Identify reusable patterns, components, and design tokens for design system extraction.

Updated Nov 25, 2025
One-click install
npx skills add https://github.com/1IssaMohamed/IEEE-YorkU --skill extract-1issamohamed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/1IssaMohamed/IEEE-YorkU/tree/main/.agents/skills/extract
Command: npx skills add https://github.com/1IssaMohamed/IEEE-YorkU --skill extract-1issamohamed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and consolidate reusable patterns, components, and design tokens to strengthen consistency across design systems and reduce duplication.

Core Features & Use Cases

  • Pattern discovery: Locate repeated UI patterns, tokens, and items that should become system-wide.
  • Tokenization plan: Define design tokens for colors, typography, spacing, and elevation to ensure consistent usage.
  • Migration guidance: Provide a step-by-step plan to replace bespoke implementations with shared components and tokens.

Quick Start

Plan a systematic extraction by identifying reusable patterns and tokens, then refactor 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 identify reusable UI patterns for a design system?

To identify reusable UI patterns for a design system, analyze target design areas to locate repeated components and assess them for extraction opportunities, consolidating them for systematic reuse.

What is a design tokenization plan and how does it work?

A design tokenization plan defines tokens for colors, typography, spacing, and elevation to ensure consistent usage. It works by assessing bespoke implementations and creating standardized tokens for system-wide design system reuse.

How do I migrate bespoke UI components into a shared design system?

To migrate bespoke UI components into a shared design system, follow a step-by-step migration plan that replaces duplicated implementations with shared components and tokens, including necessary documentation updates and naming conventions.

What should be included in a design system extraction plan?

A design system extraction plan should include components to extract, tokens to create, variants to support, naming conventions, migration steps, and documentation updates to ensure successful consolidation of reusable patterns.

When should I consolidate repeated design patterns into tokens?

You should consolidate repeated design patterns into tokens when pattern discovery reveals duplicated UI elements across target design areas, requiring tokenization to ensure consistent usage and reduce duplication.