Extract Flow
Identify reusable patterns, components, and design tokens, then extract and consolidate them into the design system for systematic reuse.
Step 1: Discover the Design System
Find the design system, component library, or shared UI directory. Understand its structure: component organization, naming conventions, design token structure, import/export conventions.
CRITICAL: If no design system exists, do not create one yet. STOP and ask the user
Step 2: Identify Patterns
Look for extraction opportunities in the target area:
- Repeated components: Similar UI patterns used 3+ times (buttons, cards, inputs)
- Hard-coded values: Colors, spacing, typography, shadows that should be tokens
- Inconsistent variations: Multiple implementations of the same concept
- Composition patterns: Layout or interaction patterns that repeat (form rows, toolbar groups, empty states)
- Type styles: Repeated font-size + weight + line-height combinations
- Animation patterns: Repeated easing, duration, or keyframe combinations
Assess value: only extract things used 3+ times with the same intent. Premature abstraction is worse than duplication.
Step 3: Plan Extraction
Create a systematic plan:
- Components to extract: Which UI elements become reusable components?
- Tokens to create: Which hard-coded values become design tokens?
- Variants to support: What variations does each component need?
- Naming conventions: Component names, token names, prop names that match existing patterns
- Migration path: How to refactor existing uses to consume the new shared versions
IMPORTANT: Design systems grow incrementally. Extract what is clearly reusable now, not everything that might someday be reusable.
Step 4: Extract & Enrich
Build improved, reusable versions:
- Components: Clear props API with sensible defaults, proper variants for different use cases, accessibility built in (ARIA, keyboard navigation, focus management), documentation and usage examples
- Design tokens: Clear naming (primitive vs semantic), proper hierarchy and organization, documentation of when to use each token
- Patterns: When to use this pattern, code examples, variations and combinations
Step 5: Migrate
Replace existing uses with the new shared versions:
- Find all instances: Search for the patterns you extracted
- Replace systematically: Update each use to consume the shared version
- Test thoroughly: Ensure visual and functional parity
- Delete dead code: Remove the old implementations
Step 6: Document
Update design system documentation:
- Add new components to the component library
- Document token usage and values
- Add examples and guidelines
- Update any Storybook or component catalog
NEVER:
- Extract one-off, context-specific implementations without generalization
- Create components so generic they are useless
- Extract without considering existing design system conventions
- Skip proper TypeScript types or prop documentation
- Create tokens for every single value (tokens should have semantic meaning)
- Extract things that differ in intent (two buttons that look similar but serve different purposes should stay separate)
1---2name: impeccable-extract3description: "Identify reusable patterns, components, and design tokens in a codebase and consolidate them into the design system for systematic reuse. Use when repeated UI has drifted into near-duplicates, or when a design system exists but is being bypassed. Discovers the existing system first and refuses to invent a new one without being told where it belongs."4license: Apache-2.05metadata:6 source: https://skillmd.com/skills/jzkk720/impeccable-extract7---89# Extract Flow1011Identify reusable patterns, components, and design tokens, then extract and consolidate them into the design system for systematic reuse.1213## Step 1: Discover the Design System1415Find the design system, component library, or shared UI directory. Understand its structure: component organization, naming conventions, design token structure, import/export conventions.1617**CRITICAL**: If no design system exists, do not create one yet. STOP and ask the user1819## Step 2: Identify Patterns2021Look for extraction opportunities in the target area:2223- **Repeated components**: Similar UI patterns used 3+ times (buttons, cards, inputs)24- **Hard-coded values**: Colors, spacing, typography, shadows that should be tokens25- **Inconsistent variations**: Multiple implementations of the same concept26- **Composition patterns**: Layout or interaction patterns that repeat (form rows, toolbar groups, empty states)27- **Type styles**: Repeated font-size + weight + line-height combinations28- **Animation patterns**: Repeated easing, duration, or keyframe combinations2930Assess value: only extract things used 3+ times with the same intent. Premature abstraction is worse than duplication.3132## Step 3: Plan Extraction3334Create a systematic plan:3536- **Components to extract**: Which UI elements become reusable components?37- **Tokens to create**: Which hard-coded values become design tokens?38- **Variants to support**: What variations does each component need?39- **Naming conventions**: Component names, token names, prop names that match existing patterns40- **Migration path**: How to refactor existing uses to consume the new shared versions4142**IMPORTANT**: Design systems grow incrementally. Extract what is clearly reusable now, not everything that might someday be reusable.4344## Step 4: Extract & Enrich4546Build improved, reusable versions:4748- **Components**: Clear props API with sensible defaults, proper variants for different use cases, accessibility built in (ARIA, keyboard navigation, focus management), documentation and usage examples49- **Design tokens**: Clear naming (primitive vs semantic), proper hierarchy and organization, documentation of when to use each token50- **Patterns**: When to use this pattern, code examples, variations and combinations5152## Step 5: Migrate5354Replace existing uses with the new shared versions:5556- **Find all instances**: Search for the patterns you extracted57- **Replace systematically**: Update each use to consume the shared version58- **Test thoroughly**: Ensure visual and functional parity59- **Delete dead code**: Remove the old implementations6061## Step 6: Document6263Update design system documentation:6465- Add new components to the component library66- Document token usage and values67- Add examples and guidelines68- Update any Storybook or component catalog6970**NEVER**:71- Extract one-off, context-specific implementations without generalization72- Create components so generic they are useless73- Extract without considering existing design system conventions74- Skip proper TypeScript types or prop documentation75- Create tokens for every single value (tokens should have semantic meaning)76- Extract things that differ in intent (two buttons that look similar but serve different purposes should stay separate)