Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fengshao1227/extract
Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.
Passed 18 of 21 test cases with the skill, and 17 of 21 without it.
1 fixed18 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Our repository has duplicate button styles in `src/views/checkout` and `src/views/account`. We want to centralize these into a component, but there is currently no `src/components` or design system folder present in the codebase. What should we do first?
| Checked | Without skill | With skill |
|---|---|---|
| The response explicitly asks the user for the preferred location and structural conventions before creating a new design system directory. | Missed | Passed |
The instructions your model reads when the skill loads.
Identify reusable patterns, components, and design tokens, then extract and consolidate them into the design system for systematic reuse.
Analyze the target area to identify extraction opportunities:
Find the design system: Locate your design system, component library, or shared UI directory (grep for "design system", "ui", "components", etc.). Understand its structure:
CRITICAL: If no design system exists, ask before creating one. Understand the preferred location and structure first.
Identify patterns: Look for:
Assess value: Not everything should be extracted. Consider:
Create a systematic extraction plan:
IMPORTANT: Design systems grow incrementally. Extract what's clearly reusable now, not everything that might someday be reusable.
test cases passed, vs 17 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.