One-click install
npx skills add https://github.com/microlinkhq/www --skill extract-microlinkhq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/microlinkhq/www/tree/main/.agents/skills/extract
Command: npx skills add https://github.com/microlinkhq/www --skill extract-microlinkhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify reusable UI patterns, tokens, and conventions buried across a codebase so your design system stays consistent and maintainable instead of drifting.

Core Features & Use Cases

  • Discovery: Finds extraction opportunities by locating your design system, analyzing component organization, and spotting repeated patterns and hard-coded styling values.
  • Planning & Refactoring: Produces a migration plan that defines components, tokens, variants, naming conventions, and how to refactor existing implementations safely.
  • Enrichment & Documentation: Creates improved reusable components with accessibility considerations, adds well-structured design tokens, and documents patterns and usage for ongoing adoption.
  • Use Case: When multiple teams implement buttons, cards, spacing, and typography differently across features, extract them into shared building blocks and tokenized styles, then migrate usage to reduce inconsistencies.

Quick Start

Use the extract skill to analyze your existing UI and refactor a targeted area into reusable components, design tokens, and documented patterns.

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 codebase?

To extract reusable UI patterns from an existing codebase, you analyze the current design system structure to locate repeated features and hard-coded styling values, then define components, variants, and naming conventions for systematic migration. This eliminates design inconsistency and duplication.

What is design token extraction and when do I need it?

Design token extraction is the process of identifying hard-coded styling values repeated across features and converting them into structured, documented design tokens. You need it when multiple teams implement typography, spacing, and colors differently, causing your UI patterns to drift and become inconsistent.

How do I plan a migration to a new design system?

You plan a design system migration by identifying extraction candidates based on reuse value, defining naming conventions and component variants, and establishing a safe migration path. This ensures existing implementations are refactored systematically without breaking current functionality.

Do I need an existing design system before extracting components?

You do not need a fully built design system beforehand. This process works effectively as long as a design system exists or is ready to be incrementally expanded, allowing you to extract components and tokens from your current codebase into shared building blocks.

Can I add accessibility considerations when refactoring UI components?

Yes, you can enrich extracted components with accessibility considerations during the refactoring process. The system creates improved reusable components and documents usage patterns, ensuring that accessibility standards are integrated into the design system during migration.

What is the best way to reduce design inconsistency across multiple teams?

The best way to reduce design inconsistency is to locate repeated UI patterns and hard-coded styles across features, extract them into shared building blocks and tokenized styles, and then migrate usage to ensure all teams implement components uniformly.