Menu
Pull reusable components and tokens into the design system
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | ui-extract |
| description | Pull reusable components and tokens into the design system |
/ui-extract [target] - Pull reusable components and tokens into the design system. Identify patterns, consolidate, migrate.
Find the design system, component library, or shared UI directory. Understand structure: organization, naming, tokens, conventions.
If no design system exists, ask before creating one.
Look for extraction opportunities:
Only extract things used 3+ times with same intent. Premature abstraction is worse than duplication.
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Surface deepening opportunities in a codebase — shallow modules, seam leaks, missing locality — and grill through whichever one you pick. Architecture-pattern aware (monolith / distributed / serverless).
Reconcile and validate all documents in the project's docs/ directory
Full-project code audit workflow: audit then fix
Systematic root cause analysis. No fixes without investigation
Principal Engineer persona. Production-first technical judgment
