extract

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

Updated Nov 13, 2023
One-click install
npx skills add https://github.com/Bloodrey41/dotfiles --skill extract-bloodrey41
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/Bloodrey41/dotfiles/tree/main/.claude/skills/extract
Command: npx skills add https://github.com/Bloodrey41/dotfiles --skill extract-bloodrey41

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. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.

Core Features & Use Cases

  • Identify repeated UI patterns across a project and consolidate them into reusable components.
  • Detect hard-coded values (colors, spacing, typography) and propose design tokens to improve consistency.
  • Provide a migration plan to replace existing implementations with shared, canonical versions and document the updated design system.

Quick Start

Provide a target area or design library name and I will identify reusable patterns and generate a plan to consolidate them into the 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 UI patterns from an existing project to build a design system?

To extract reusable UI patterns, analyze your target UI space to locate repeated visual structures and consolidate them into a design system. This process identifies opportunities for shared components, design tokens, and systematic reuse across your project.

What is the best way to identify repeated UI components and consolidate them into a component library?

The best way to consolidate repeated UI components is to analyze the target UI space for shared patterns and generate a migration plan. This plan replaces existing duplicate implementations with shared, canonical versions and documents the updated component library.

How do I create a migration plan for refactoring hard-coded values into design tokens?

A migration plan for design tokens includes component extraction, token creation, naming conventions, and usage guidelines. It provides a structured approach to replace existing hard-coded implementations with shared, canonical versions systematically.

Can I use this approach to document naming conventions and usage guidelines for my design system?

Yes, you can document naming conventions and usage guidelines for your design system during the consolidation process. The migration plan explicitly includes establishing these standards to ensure systematic reuse and maintainability across components and tokens.