extract

Extract reusable components, design tokens, and patterns into a design system.

1|Updated Oct 20, 2024
One-click install
npx skills add https://github.com/SteveChandler/quiver --skill extract-stevechandler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/SteveChandler/quiver/tree/main/.agents/skills/extract
Command: npx skills add https://github.com/SteveChandler/quiver --skill extract-stevechandler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate duplicated UI patterns, hard-coded style values, and inconsistent component variations that increase maintenance cost and visual inconsistency. This Skill identifies those repeated 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, typography, and inconsistent variations of the same concept. - Component & Token Extraction: Builds reusable components with typed props, variants, accessibility support, and semantic design tokens with clear naming. - Migration & Documentation: Replaces existing implementations with shared versions, removes dead code, and updates component library documentation. - Use Case: A team finds three different button implementations across their app. Use this Skill to consolidate them into one typed, accessible Button component with variants, then migrate all call sites. ## Quick Start Ask the assistant to analyze the UI components in this project and extract repeated patterns 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 an existing codebase?▼

Identify UI patterns used three or more times, then create shared components with clear props APIs, 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?▼

Find repeated hard-coded colors, spacing, typography, and shadows, 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 a UI pattern not be extracted into a design system?▼

Avoid extracting one-off, context-specific implementations or patterns used fewer than three times. Components that are overly generic or lack 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, component organization, and naming conventions before extracting anything into a new shared library.

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

Search for all instances of the extracted pattern, update each use to consume the shared version, and test for visual and functional parity. Remove the old implementations once migration is verified.