extract

Identify reusable components and design tokens for consolidation into a design system.

1|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/navikt/watson-sak-frontend --skill extract-navikt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/navikt/watson-sak-frontend/tree/main/.agents/skills/extract
Command: npx skills add https://github.com/navikt/watson-sak-frontend --skill extract-navikt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract and consolidate reusable components, design tokens, and patterns into your design system to reduce duplication and improve consistency.

Core Features & Use Cases

  • Identify and consolidate reusable components and tokens across projects
  • Enrich the design system documentation and governance
  • Plan and migrate existing implementations to shared assets

Quick Start

Identify opportunities for reuse and initiate a consolidation plan within your design system.

Frequently Asked Questions about extract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consolidate duplicate design tokens across multiple projects?

To consolidate duplicate design tokens across multiple projects, you identify reusable patterns and extract them into a centralized design system. This process includes detecting duplication, aligning tokens, and generating migration guidance for existing implementations.

What is the best way to extract reusable components into a design system?

The best way to extract reusable components is to identify shared patterns across your codebase and plan their migration into a shared component library. This approach ensures component extraction is structured and accompanied by necessary documentation updates.

How do I plan a migration to a centralized component library?

You plan a migration to a centralized component library by detecting existing duplicate implementations and mapping them to shared assets. This provides a clear plan for component extraction, token creation, and updating project documentation.

Can I use this for design-system maintenance and token governance?

Yes, you can use this for design-system maintenance and token governance across projects. It supports identifying reusable patterns, consolidating duplicates, aligning tokens, and enriching design system documentation to maintain long-term consistency.

How do I enrich design system documentation during pattern extraction?

You enrich design system documentation during pattern extraction by consolidating identified components and tokens into a centralized repository. This ensures governance and documentation updates are applied directly alongside the extracted shared assets.