extract

Extract reusable components and design tokens into a centralized design system.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jimmy706/slide-forge --skill extract-jimmy706
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/jimmy706/slide-forge/tree/main/.agents/skills/extract
Command: npx skills add https://github.com/jimmy706/slide-forge --skill extract-jimmy706

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of inconsistent UI elements and duplicated effort by identifying and consolidating reusable components, design tokens, and patterns into a centralized design system.

Core Features & Use Cases

  • Pattern Identification: Automatically scans code and designs to find repeated UI elements and hard-coded values.
  • Design Token Creation: Converts hard-coded values (colors, spacing, typography) into systematic design tokens.
  • Component Extraction: Transforms identified patterns into reusable, well-documented components.
  • Use Case: A team can use this Skill to analyze a new feature's UI, identify buttons and color usages that are already part of their design system, and ensure they are leveraged correctly, maintaining brand consistency and reducing development time.

Quick Start

Use the extract skill to identify and consolidate reusable components from the 'user-profile' feature.

Frequently Asked Questions about extract

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

FAQPage Schema
What are design tokens and how do they improve UI consistency?

Pattern identification scans code and designs to find repeated UI elements and hard-coded values, converting them into systematic design tokens and reusable components to eliminate inconsistent variations and duplicated effort.

What is the best way to identify repeated UI elements for systematic reuse?

Yes, you can target specific feature areas like a user profile for component extraction, scanning its UI to identify buttons and color usages, ensuring they leverage the design system correctly to maintain brand consistency.

Do I need an existing component library to extract design tokens?

The best way to identify repeated UI elements is scanning code and designs for hard-coded values and inconsistent variations, then planning extraction with a focus on naming conventions, variants, and accessibility.

How do I extract reusable components and design tokens from existing UI code?

You do not need an existing component library to start extracting design tokens, as the process identifies hard-coded values and repeated patterns first, then enriches the component library through systematic consolidation.