extract

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

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/yckkkk/reo --skill extract-yckkkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/extract
Command: npx skills add https://github.com/yckkkk/reo --skill extract-yckkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify and consolidate reusable components, design tokens, and patterns into your design system, reducing duplication and enriching consistency across projects.

Core Features & Use Cases

  • Identify repeated UI patterns (components, tokens, and patterns) across projects.
  • Extract and consolidate them into a shared design system, establishing a single source of truth.
  • Plan extraction and migration with documented guidelines for naming, variants, and usage.
  • Document updated components and tokens to support future maintenance.

Quick Start

Identify a target area in your design system and begin extracting reusable components to enrich your shared library.

Frequently Asked Questions about extract

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

FAQPage Schema
How do I extract and consolidate reusable UI components into a design system?

To extract and consolidate reusable UI components into a design system, identify repeated patterns across projects and migrate them into a shared library using structured discovery, clear naming conventions, and safe refactoring practices to establish a single source of truth.

What is the best way to identify repeated design patterns and tokens across projects?

Identifying repeated design patterns and tokens across projects involves a structured discovery workflow that audits existing UI elements, extracts duplicated components and variables, and documents them systematically to reduce redundancy and enrich consistency.

How do I create and document design tokens for systematic reuse?

Creating and documenting design tokens for systematic reuse requires extracting identified variables into the consolidated design system, establishing clear naming conventions and variants, and generating usage documentation to support future maintenance and safe refactoring.

Can I use this extraction workflow to upgrade an existing component library?

Yes, you can use this extraction workflow to upgrade an existing component library by applying its structured migration process to safely refactor current components, update variants, and document changes while maintaining system consistency.

Does extracting design system components require specific dependencies or environments?

Extracting design system components requires no specific external dependencies or environments, as the workflow focuses on applying structured discovery, naming conventions, and documentation guidelines directly to your existing design and development projects.