extract

Name: extract
Availability: InStock
Author: raphaelmans

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

Updated Feb 28, 2026

Search Tags:#components #patterns #governance #tokens #design-system #reuse #extract

Ready to run

npx skills add https://github.com/raphaelmans/agent-skills --skill extract-raphaelmans

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/raphaelmans/agent-skills/tree/main/extract
Command: npx skills add https://github.com/raphaelmans/agent-skills --skill extract-raphaelmans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and consolidate patterns, components, and design tokens into a cohesive design system to enable systematic reuse across projects.

Core Features & Use Cases

Analyze design libraries to surface repeated UI patterns, token values, and component variations.
Define a clear extraction plan with naming conventions, token semantics, and migration steps.
Use-case: teams audit a component catalog and consolidate assets into a centralized, reusable library.

Quick Start

Identify reusable patterns, components, and design tokens in the target area and consolidate them into the design system for systematic reuse.

Frequently Asked Questions about extract

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

FAQPage Schema

How do I extract reusable design tokens from an existing UI catalog?▼

Consolidate design tokens by auditing your UI catalog to identify repeated values and component variations. The extraction process defines token semantics, naming conventions, and migration steps to unify these assets into a centralized, reusable design system library.

What is the best way to audit a component library for design system consolidation?▼

Audit a component library by analyzing its contents to surface repeated UI patterns and component variations. This identifies consolidation opportunities and generates an extraction plan with naming conventions and migration steps to centralize reusable assets into the design system.

How do I create a migration plan for consolidating UI patterns into a design system?▼

Create a migration plan by defining an extraction strategy that covers component naming, token semantics, and step-by-step migration actions. This documents usage guidelines and unifies reusable patterns into a cohesive design system for systematic reuse across projects.

When do I need to consolidate design tokens and components into a centralized library?▼

Consolidate design tokens and components when repeated UI patterns and token values appear across multiple projects. Centralizing these assets into a unified library enables systematic reuse and establishes clear governance over the design system.

Can I use this approach to define naming conventions for a token inventory?▼

Yes, this approach defines naming conventions for a token inventory by establishing token semantics and component naming rules. It documents usage guidelines to ensure consistent governance across the consolidated design system.