extract

Extract reusable components and design tokens into a design system.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/AkaraChen/proxy-up --skill extract-akarachen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/AkaraChen/proxy-up/tree/main/.agents/skills/extract
Command: npx skills add https://github.com/AkaraChen/proxy-up --skill extract-akarachen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repeated UI patterns, hard-coded style values, and inconsistent component implementations accumulate across a codebase, making interfaces harder to maintain and evolve. This Skill identifies those patterns and consolidates them into a shared design system. ## Core Features & Use Cases - Pattern Discovery: Scans the codebase for repeated components, hard-coded colors, spacing, and typography values that should become design tokens. - Component Extraction: Builds reusable components with typed props, variants, accessibility support, and documentation matching existing conventions. - Systematic Migration: Replaces existing one-off implementations with the shared versions and updates design system documentation. - Use Case: You notice three different button implementations across your app. Use this Skill to consolidate them into one typed, accessible Button component with variants, create tokens for the hard-coded colors, and migrate all call sites. ## Quick Start Ask the assistant to extract the repeated button and card patterns in the src directory 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 components from repeated UI patterns?▼

Identify UI patterns used three or more times, then create a shared component with a clear props API, variants, and accessibility support. Replace each existing instance with the shared version and delete the old implementations.

How to convert hard-coded CSS values into design tokens?▼

Scan the codebase for repeated colors, spacing, typography, and shadow values, then create tokens with clear primitive and semantic naming. Document when to use each token rather than creating tokens for every single value.

When should I not extract a component into a design system?▼

Avoid extracting one-off, context-specific implementations or patterns used fewer than three times. Overly generic components and tokens without semantic meaning add maintenance cost without improving consistency.

What if my project has no design system yet?▼

The Skill asks before creating one, since location and structure matter. Confirm the preferred directory, naming conventions, and organization first, then extract only what is clearly reusable now.

How do I migrate existing code to use shared components?▼

Search for all instances of the extracted pattern, replace each use with the shared component, and verify visual and functional parity. Remove the old implementations once migration is complete.