extract

Extract reusable UI components and design tokens from a codebase.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/niiiusburo/Tgroup --skill extract-niiiusburo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/niiiusburo/Tgroup/tree/main/website/.agents/skills/extract
Command: npx skills add https://github.com/niiiusburo/Tgroup --skill extract-niiiusburo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds repeated UI patterns and hard-coded values that should become shared components or tokens, reducing duplication, inconsistency, and one-off implementations.

Core Features & Use Cases

  • Detects reusable components such as buttons, cards, inputs, and layout patterns.
  • Identifies design tokens for spacing, color, typography, and shadows.
  • Plans extraction, migration, and documentation so the design system grows safely.
  • Use it when a product has several similar implementations of the same UI behavior and needs one consistent shared version.

Quick Start

Use the extract skill on the target app or folder to identify repeated UI patterns and turn them into reusable design system components and tokens.

Frequently Asked Questions about extract

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

FAQPage Schema
How do I extract reusable UI components from a codebase with repeated interface elements?

Design tokens standardize hard-coded visual values for spacing, color, typography, and shadows. The Skill identifies these repeated hard-coded values across your codebase and plans their consolidation into shared design tokens, reducing inconsistency and one-off implementations.

What's the best way to refactor repeated UI patterns into a design system?

Yes, you can use it on any target app or folder that contains several similar implementations of the same UI behavior. It works by identifying repeated UI patterns and hard-coded visual values that should become shared components or tokens, regardless of the specific product context.

How does component extraction handle migration of existing usages?

Use this refactoring approach when a product has several similar implementations of the same UI behavior and needs one consistent shared version. If your codebase suffers from duplication, inconsistency, and one-off visual implementations, extraction will consolidate them into a unified design system.

What design tokens can be identified when extracting reusable UI patterns?

When extracting reusable UI patterns, the Skill identifies design tokens for spacing, color, typography, and shadows. It detects these hard-coded visual values across your codebase and plans their standardization to reduce visual inconsistency and consolidate shared design assets.