Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
Extract and consolidate reusable components, design tokens, and patterns into your design system.
Install I Extract
$ npx skills add boussadjra/vuestrata --skill i-extract -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install boussadjra/vuestrata i-extract --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/i-extract .claude/skills/i-extract && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "i-extract" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-extract into .claude/skills/i-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-extract", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-extractType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add boussadjra/vuestrata --skill i-extract -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install boussadjra/vuestrata i-extract --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/i-extract .agents/skills/i-extract && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "i-extract" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-extract into .agents/skills/i-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-extract", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boussadjra/vuestrata --skill i-extract -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install boussadjra/vuestrata i-extract --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/i-extract .cursor/skills/i-extract && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "i-extract" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-extract into .cursor/skills/i-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-extract", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/boussadjra/vuestrata.git --path .github/skills/i-extract--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add boussadjra/vuestrata --skill i-extract -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install boussadjra/vuestrata i-extract --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/i-extract .gemini/skills/i-extract && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "i-extract" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-extract into .gemini/skills/i-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-extract", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install boussadjra/vuestrata i-extractInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add boussadjra/vuestrata --skill i-extract -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/i-extract .github/skills/i-extract && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "i-extract" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-extract into .github/skills/i-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-extract", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boussadjra/vuestrata --skill i-extract -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install boussadjra/vuestrata i-extract --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/i-extract .opencode/skills/i-extract && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "i-extract" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-extract into .opencode/skills/i-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-extract", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
i-extract- GitHub stars
- 111
- Used in
- 7 other repos
- Token cost
- ~959 tokens
- SKILL.md length
- 444 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Extract and consolidate reusable components, design tokens, and patterns into your design system.
- Works in 3 steps: Find the design system: Locate your… → Identify patterns: Look for → Assess value: Not everything should be…
- Tasks that involve Design systems
- SKILL.md covers Discover, Plan Extraction, Extract & Enrich and Migrate, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
I Extract is an agent skill from boussadjra/vuestrata. Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Design systems and Design tokens. The repository describes itself as: A modern, production-ready Vue 3 template with multi-theme support, Reka UI wrappers, and enterprise-grade tooling. The licence is MIT.
When your agent uses it
- Tasks that involve Design systems
- Tasks that involve Design tokens
Example prompts
- “/i-extract”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Find the design system: Locate your design system, component library, or shared UI directory (grep for "design system", "ui"…
- Identify patterns: Look for
- Assess value: Not everything should be extracted. Consider
What it can do on your machine
Read from SKILL.md and the folder at commit 73cbf9f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
I Extract loads about 959 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 444 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from boussadjra/vuestrata at commit 73cbf9f, republished under its MIT licence (© boussadjra). 444 words, ~959 tokens.
Download SKILL.mdSave it as
.claude/skills/i-extract/SKILL.md (or your agent's skills folder).- name
- i-extract
- description
- Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.
- user-invokable
- true
- argument-hint
- TARGET=<value>
Identify reusable patterns, components, and design tokens, then extract and consolidate them into the design system for systematic reuse.
Discover
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:
- Component organization and naming conventions
- Design token structure (if any)
- Documentation patterns
- Import/export conventions
CRITICAL: If no design system exists, ask before creating one. Understand the preferred location and structure first.
Identify patterns: Look for:
- Repeated components: Similar UI patterns used multiple times (buttons, cards, inputs, etc.)
- Hard-coded values: Colors, spacing, typography, shadows that should be tokens
- Inconsistent variations: Multiple implementations of the same concept (3 different button styles)
- Reusable patterns: Layout patterns, composition patterns, interaction patterns worth systematizing
Assess value: Not everything should be extracted. Consider:
- Is this used 3+ times, or likely to be reused?
- Would systematizing this improve consistency?
- Is this a general pattern or context-specific?
- What's the maintenance cost vs benefit?
Plan Extraction
Create a systematic extraction plan:
- Components to extract: Which UI elements become reusable components?
- Tokens to create: Which hard-coded values become design tokens?
- Variants to support: What variations does each component need?
- Naming conventions: Component names, token names, prop names that match existing patterns
- Migration path: How to refactor existing uses to consume the new shared versions
IMPORTANT: Design systems grow incrementally. Extract what's clearly reusable now, not everything that might someday be reusable.
Show full SKILL.md (198 more words)Show less
Extract & Enrich
Build improved, reusable versions:
- Components: Create well-designed components with:
- Clear props API with sensible defaults
- Proper variants for different use cases
- Accessibility built in (ARIA, keyboard navigation, focus management)
- Documentation and usage examples
- Design tokens: Create tokens with:
- Clear naming (primitive vs semantic)
- Proper hierarchy and organization
- Documentation of when to use each token
- Patterns: Document patterns with:
- When to use this pattern
- Code examples
- Variations and combinations
NEVER:
- Extract one-off, context-specific implementations without generalization
- Create components so generic they're useless
- Extract without considering existing design system conventions
- Skip proper TypeScript types or prop documentation
- Create tokens for every single value (tokens should have semantic meaning)
Migrate
Replace existing uses with the new shared versions:
- Find all instances: Search for the patterns you've extracted
- Replace systematically: Update each use to consume the shared version
- Test thoroughly: Ensure visual and functional parity
- Delete dead code: Remove the old implementations
Document
Update design system documentation:
- Add new components to the component library
- Document token usage and values
- Add examples and guidelines
- Update any Storybook or component catalog
Remember: A good design system is a living system. Extract patterns as they emerge, enrich them thoughtfully, and maintain them consistently.
© boussadjra, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/i-extract of boussadjra/vuestrata.
Open the folder on GitHubat commit 73cbf9f
Used in 7 other repositories
We found 7 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 7 other GitHub owners. This page covers the copy in boussadjra/vuestrata, which our catalogue first saw on October 7, 2026.
Compare with similar skills
I Extract next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| I Extract this skillboussadjra/vuestrata | 111 | 7 repos | ~959 | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Figma use_figma Plugin API Ruleswarpdotdev/warp | 65k | 4 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Design SystemOhh-889/skyroc | 795 | 11 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Design Dnazanwei/design-dna | 1.9k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Scalar Design Systemscalar/scalar | 16k | — | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
Design System
Ohh-889/skyroc
Token architecture, component specifications, and slide generation.
Design Dna
zanwei/design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects…
Scalar Design System
scalar/scalar
Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library.
- Official
Stitch Taste Design System
google-labs-code/stitch-skills
Generates a DESIGN.md design-language file for Google Stitch that encodes color, typography, layout, component behavior and motion rules to avoid generic AI-looking UI.
More from boussadjra/vuestrata
All 21 skills in this repoI Delight
boussadjra/vuestrata
Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use.
I Optimize
boussadjra/vuestrata
Improve interface performance across loading speed, rendering, animations, images, and bundle size.
I Frontend Design
boussadjra/vuestrata
Create distinctive, production-grade frontend interfaces with high design quality.
I Harden
boussadjra/vuestrata
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management.
I Onboard
boussadjra/vuestrata
Design or improve onboarding flows, empty states, and first-time user experiences.
I Teach Impeccable
boussadjra/vuestrata
One-time setup that gathers design context for your project and saves it to your AI config file.
Related
Categories
Questions about I Extract
What does I Extract do?
Extract and consolidate reusable components, design tokens, and patterns into your design system. I Extract is an agent skill from boussadjra/vuestrata. Extract and consolidate reusable components, design tokens, and patterns into your design system.
When should I use I Extract?
I Extract fits situations like: tasks that involve Design systems; tasks that involve Design tokens.
How do I install I Extract in Claude Code?
Run `npx skills add boussadjra/vuestrata --skill i-extract -a claude-code`. Or copy the skill folder (.github/skills/i-extract in boussadjra/vuestrata) into .claude/skills/i-extract in your project. Claude Code loads it when a task matches its description.
How do I install I Extract in Codex?
Run `npx skills add boussadjra/vuestrata --skill i-extract -a codex`. Or copy the skill folder (.github/skills/i-extract in boussadjra/vuestrata) into .agents/skills/i-extract in your project. Codex loads it when a task matches its description.
Can I use I Extract in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add boussadjra/vuestrata --skill i-extract -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/i-extract, .gemini/skills/i-extract, .github/skills/i-extract and .opencode/skills/i-extract in your project.
What does I Extract need to run?
SKILL.md names no scripts, command-line tools or credentials: I Extract is instructions for the agent only.
Does I Extract access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is I Extract safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does I Extract use?
I Extract is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does I Extract use?
About 959 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to I Extract?
Skills that share tags, products or a category with I Extract: Figma Design System Builder (warpdotdev/warp, 65k stars), Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars), Design System (Ohh-889/skyroc, 795 stars) and Design Dna (zanwei/design-dna, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains I Extract?
boussadjra (a GitHub user) maintains it in boussadjra/vuestrata, which has 111 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 5, 2026.
Source: boussadjra/vuestrata on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.