extract

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.

Core Features & Use Cases

  • Identify repeated components, patterns, and hard-coded values that should become tokens
  • Consolidate components and tokens into a central design system to improve consistency and speed
  • Plan migration, documentation, and governance to enable reuse across teams

Quick Start

Analyze your codebase to locate repeated design patterns and tokens, then consolidate them into a shared 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 reusable UI components and tokens into a design system?

To consolidate reusable UI components and tokens, analyze your codebase to identify repeated patterns and hard-coded values, then centralize them into a shared design system to improve consistency and speed across multi-team projects.

What are design tokens and when do I need to extract them?

Design tokens are reusable variables for hard-coded values like colors and spacing. You need to extract them when repeated UI patterns and values fragment consistency, requiring systematic consolidation into a central library for multi-team adoption.

How do I plan migration for a component library?

Plan component library migration by inventorying existing components and tokens, identifying refactor opportunities for systematic reuse, and generating documentation and governance plans to enable adoption across teams.

Can I use design system extraction for multi-team projects?

Yes, design system extraction is applicable to multi-team design projects where consistency and systematic reuse across components, tokens, and layouts are needed to ensure unified UI patterns and centralized governance.

What is the best way to identify repeated design patterns in a codebase?

The best way to identify repeated design patterns is to analyze your codebase to locate duplicated components and hard-coded values, consolidating these extracted tokens into a central design system for systematic reuse.

How do I generate documentation to enable design system adoption?

Generate design system documentation by inventorying consolidated components and tokens, then planning governance and migration guides to enable systematic reuse and adoption across multiple teams.