extract

Extract reusable components, design tokens, and patterns from a codebase.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/oliverjone01-dev/t1 --skill extract-oliverjone01-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/oliverjone01-dev/t1/tree/main/.claude/skills/extract
Command: npx skills add https://github.com/oliverjone01-dev/t1 --skill extract-oliverjone01-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds repeated interface patterns, hard-coded values, and duplicated behavior so you can turn them into shared building blocks instead of maintaining the same logic in many places.

Core Features & Use Cases

  • Pattern discovery: Detect repeated components, layouts, and interaction patterns across a feature or product area.
  • Token extraction: Convert hard-coded colors, spacing, and other values into meaningful design tokens.
  • System consolidation: Replace one-off implementations with documented shared components and consistent variants.
  • Use case: Use it when a checkout flow, dashboard, or form suite has multiple copies of the same UI pattern and needs a cleaner design system.

Quick Start

Ask the extract skill to review a target area and consolidate repeated components, tokens, and patterns into the 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 extract reusable components from a codebase with repeated UI patterns?▼

You can extract design tokens from hard-coded values by discovering repeated colors and spacing across your codebase, then converting them into a meaningful semantic token hierarchy that supports UI consistency and systematic refactoring.

When do I need to consolidate duplicated UI into a shared design system?▼

Pattern discovery for design system refactoring works by detecting repeated components, layouts, and interaction patterns across a product area, then replacing one-off implementations with documented shared components and consistent variants for UI consistency.

Can I use this approach to refactor hard-coded colors and spacing into design tokens?▼

Yes, you can refactor hard-coded colors and spacing into design tokens by analyzing repeated usage in your codebase, establishing a semantic token hierarchy, and migrating existing instances to ensure consistent variants across the shared UI library.

What's the best way to document component APIs and accessibility considerations during token extraction?▼

The best way to document component APIs and accessibility considerations during token extraction is to consolidate one-off implementations into documented shared components, ensuring the semantic token hierarchy supports accessibility and consistent variants.