extract

Extract reusable UI patterns, design tokens, and component templates into a centralized design system.

1|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/sandrasocial/sselfie-9g --skill extract-sandrasocial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/sandrasocial/sselfie-9g/tree/main/.agents/skills/extract
Command: npx skills add https://github.com/sandrasocial/sselfie-9g --skill extract-sandrasocial

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams struggle to identify and consolidate recurring UI elements, tokens, and patterns into a cohesive, maintainable design system.

Core Features & Use Cases

  • Extraction planning: Analyze projects to surface reusable components, tokens, and patterns, and produce a structured plan.
  • Enrichment & consolidation: Create enriched, reusable component definitions and token sets ready for adoption.
  • Migration & documentation: Provide a migration path and updated design-system documentation to guide teams.

Quick Start

Analyze your project to identify reusable UI components and tokens, then generate a consolidated extraction plan.

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 into a design system?

To extract reusable UI patterns, analyze your project to identify recurring components and design tokens, then generate a structured extraction plan to consolidate them into a centralized design system.

What is the best way to consolidate design tokens and component templates from multiple projects?

Consolidating design tokens and component templates involves identifying shared UI patterns across projects, enriching them into reusable definitions, and producing a migration path for centralized design system adoption.

How do I plan a design system migration for existing components?

Planning a design system migration requires analyzing your current component library to surface reusable assets, then mapping out a structured migration path and updating documentation to guide the transition.

Can I generate design system documentation from my existing component library?

Yes, generating design system documentation is achieved by analyzing your existing component library to identify reusable UI patterns, which are then consolidated into enriched definitions and updated design system documentation.

Does this approach work for projects with multiple similar components and tokens?

Yes, this approach is specifically designed for design system initiatives with multiple similar components, tokens, and patterns, producing an extraction plan and migration path to ensure maintainable consolidation.