Skills extract
📦

extract

Content revision r1 Safe

Extract Reusable Design System Patterns

Teams often duplicate UI components, tokens, and layout patterns across an application. This skill helps Claude, Codex, or Claude Code find reusable patterns and consolidate them into a maintained design system.

Supports: Claude Codex Code(CC)
🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "extract" from https://skillstore.io/skills/pbakaus-extract.md and its manifest at https://skillstore.io/api/skills/pbakaus-extract/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/pbakaus-extract.md Signed manifest GET /api/skills/pbakaus-extract/manifest Signed lockfile GET /api/skills/pbakaus-extract/lockfile

Test it

Using "extract". Review the checkout flow for reusable UI patterns.

Expected outcome:

Findings include repeated summary cards, duplicate button variants, and hard-coded spacing. Recommended extraction starts with summary card and checkout action components.

Using "extract". Extract design tokens from the settings pages.

Expected outcome:

The skill would propose semantic spacing, surface, text, and focus tokens, then map existing settings page values to those names.

Using "extract". Move repeated profile components into the component library.

Expected outcome:

The result would include a migration plan, reusable component boundaries, variant guidance, documentation updates, and a checklist for replacing old usages.

Security Audit

Safe
v4 • 7/6/2026 Open versioned report

The single static finding is a false positive. SKILL.md line 71 warns against creating overly generic components, and no network reconnaissance behavior or prompt injection content was found.

1
Files scanned
96
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/pbakaus-extract/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/pbakaus-extract/security.svg)](https://skillstore.io/skills/pbakaus-extract?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/pbakaus-extract?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/pbakaus-extract/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/pbakaus-extract.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

pbakaus. (2026). extract security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/pbakaus-extract/audits/4

BibTeX citation

@techreport{pbakaus-pbakaus-extract-2026, author = {pbakaus}, title = {extract security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/pbakaus-extract/audits/4}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "extract security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "pbakaus" date-released: "2026-07-06" url: "https://skillstore.io/skills/pbakaus-extract/audits/4" identifiers: - type: other value: "skillstore:pbakaus-extract:audit:4" description: "Skillstore immutable audit report identifier"

Compare variants

3 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
pbakaus Recommended Current

pbakaus-extract

Skillstore Score 79
Evidence Confidence High
Skillstore usage 12
Updated

2026-08-21

tavily-ai

tavily-ai-extract

Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 10
Updated

2026-08-21

actionbook

actionbook-extract

Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 2
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
91
Spec Compliance

What You Can Build

Consolidate Duplicate Components

Find repeated UI patterns and turn them into shared components with documented variants.

Grow a Token System

Convert repeated colors, spacing, typography, and shadows into named design tokens.

Plan a UI Cleanup

Review a feature area and create a practical migration plan for reusable patterns.

Try These Prompts

Find Extraction Candidates 
Use the extract skill on {target}. Identify repeated components, hard-coded design values, and reusable layout patterns. Summarize what should be extracted first.
Plan Component Reuse 
Use the extract skill to create an extraction plan for {target}. Include proposed components, variants, prop names, token needs, and migration steps.
Build Shared Components 
Use the extract skill to implement the approved extraction plan for {target}. Match existing design system conventions, add accessibility support, and update documentation.
Migrate and Document Patterns 
Use the extract skill to replace old implementations in {target} with shared components and tokens. Confirm visual parity, remove dead code, and update catalog examples.

Best Practices

  • Start with patterns used three or more times or likely to be reused soon.
  • Match existing component, token, import, and documentation conventions.
  • Test visual and functional parity before deleting old implementations.

Avoid

  • Do not extract one-off UI that has no clear reuse value.
  • Do not create generic components without a clear product purpose.
  • Do not turn every hard-coded value into a token without semantic meaning.

Frequently Asked Questions

Does this skill create a design system from scratch?
It can help plan one, but it should ask before creating a new design system.
Can it work with an existing component library?
Yes. It first locates existing shared UI structure and follows local conventions.
What kinds of patterns does it extract?
It focuses on repeated components, design tokens, layout patterns, and inconsistent UI variants.
Does it handle accessibility?
Yes. The skill directs reusable components to include ARIA, keyboard navigation, and focus management where relevant.
Will it update documentation?
Yes. It can add examples, guidelines, and Storybook or component catalog entries when those tools exist.
How should I choose a target?
Choose a feature, component group, or application area with visible duplication or inconsistent UI patterns.

Developer Details

Author

pbakaus

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/pbakaus/impeccable/tree/main/source/skills/extract/

Ref

e397ce5a135369cd6def89cb6400d013e2f68f2f

Maintenance freshness

7/18/2026

Usage

8 downloads · 120 views

File structure

📄 SKILL.md

More from pbakaus

View all

Related Skills

View all