i-extract

Identify and extract reusable UI components and design tokens from codebases.

1|Updated Feb 6, 2025
One-click install
npx skills add https://github.com/marpme/stimmlage --skill i-extract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i-extract
Source: https://github.com/marpme/stimmlage/tree/main/.claude/skills/i-extract
Command: npx skills add https://github.com/marpme/stimmlage --skill i-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Pattern Identification: Analyzes code to find repeated UI elements, hard-coded values, and inconsistent variations.
  • Design System Enrichment: Extracts identified patterns into well-defined, reusable components and design tokens.
  • Use Case: A team notices multiple slightly different button styles across their application. This Skill can identify these variations, propose a standardized button component with configurable props, and help migrate existing usages to the new component.

Quick Start

Use the i-extract skill to identify and plan the extraction of reusable components from the 'src/components' directory.

Frequently Asked Questions about i-extract

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

FAQPage Schema
How do I extract reusable UI components from existing source code?

To extract reusable UI components from source code, analyze the codebase for repeated UI elements, hard-coded values, and inconsistent variations to plan their migration into standardized, documented design system assets.

What is the best way to identify hard-coded values and inconsistent UI patterns for a design system?

Identifying hard-coded values and inconsistent UI patterns involves pattern recognition analysis across the codebase to find duplicated elements, enabling their extraction into centralized design tokens and well-defined components.

How do I consolidate multiple slightly different button styles into a single component?

Consolidating multiple button styles requires analyzing the codebase for inconsistent variations, proposing a standardized button component with configurable props, and migrating existing usages to the new component.

Can I use pattern recognition to enrich a design system with tokens from a specific directory?

Yes, you can use pattern recognition to enrich a design system by analyzing a specific directory, like 'src/components', to extract identified patterns into well-defined, reusable components and design tokens.

When do I need to systematize UI reuse across my application?

You need to systematize UI reuse when you encounter inconsistent and duplicated UI elements within your codebase, requiring the extraction of repeated patterns into a centralized design system for systematic reuse.