extract

Extract repeated UI patterns into reusable components and shared design tokens.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Nweremizu/ekklesia --skill extract-nweremizu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/Nweremizu/ekklesia/tree/main/.junie/skills/extract
Command: npx skills add https://github.com/Nweremizu/ekklesia --skill extract-nweremizu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn repetitive UI code into reusable components and shared tokens, reducing duplication and making frontends easier to maintain.

Core Features & Use Cases

  • Pattern extraction: Detect repeated Tailwind class combinations and repeated markup that should become a component or variant.
  • Token consolidation: Identify literal magic values such as colors, spacing, shadows, font sizes, and z-index values that should move into theme tokens or CSS variables.
  • Call-site migration: Update every place that uses the extracted pattern so the refactor is complete and consistent.
  • Use case: When a dashboard page repeats the same card styling, button treatment, or layout block across several files, this Skill can extract the pattern into a named component and align all usages with the project’s existing conventions.

Quick Start

Ask the extract skill to scan the target UI for repeated patterns, extract reusable components and tokens, and update every call-site to match the project’s conventions.

Frequently Asked Questions about extract

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

FAQPage Schema
How do I extract repeated Tailwind classes into reusable components?

To extract repeated Tailwind classes into reusable components, the Skill scans your target UI to detect duplicate markup and class combinations, normalizes them into shared design tokens, and updates every call-site to match project conventions for a complete migration.

What is the best way to consolidate magic values into design tokens during a frontend refactor?

Consolidating magic values into design tokens involves identifying literal colors, spacing, shadows, and z-index values in your codebase, normalizing them into theme tokens or CSS variables, and replacing all literal instances to align with your project's existing conventions.

Can I update all call-sites automatically when extracting UI patterns?

Yes, you can update call-sites during pattern extraction. The Skill ensures a complete and consistent migration by applying project-convention matching and updating every place that uses the extracted repeated markup or Tailwind class combination.

When do I need to refactor UI patterns into shared tokens and components?

You need to refactor UI patterns into shared tokens when your frontend exhibits class duplication, repeated markup, and magic values. This consolidation is necessary when the same styling or layout blocks are repeated across multiple files and require alignment.

Does component extraction work with existing project conventions?

Yes, component extraction works with existing project conventions. The Skill requires project-convention matching to ensure the extracted reusable components, variants, and shared design tokens integrate seamlessly without disrupting your current codebase standards.

What are the limitations of extracting UI patterns from a frontend codebase?

The primary limitation of extracting UI patterns is the dependency on thorough call-site migration. A successful refactor requires complete updates to every usage location; otherwise, the extracted components and normalized tokens will result in an inconsistent codebase.