skills.rest
GuiErba
GuiErbaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

component-common-domain-detection

Detect duplicate domain logic across components and propose consolidation plans.

Updated May 28, 2022
Search Tags:#architecture#components#refactor#pattern#duplication#consolidation#domain
One-click install
npx skills add https://github.com/GuiErba/guierba.github.io --skill component-common-domain-detection-guierba
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: component-common-domain-detection
Source: https://github.com/GuiErba/guierba.github.io/tree/main/new/.cursor/skills/component-common-domain-detection
Command: npx skills add https://github.com/GuiErba/guierba.github.io --skill component-common-domain-detection-guierba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill identifies and reduces duplication by locating common domain logic across multiple components and proposing consolidation opportunities to improve maintainability and reduce technical debt.

Core Features & Use Cases

  • Scan component namespaces for common leaf patterns like *.notification, *.audit, and *.validation to surface duplication.
  • Detect shared domain classes used across multiple components to identify cross-cutting reuse opportunities.
  • Analyze functionality similarity and assess coupling impact to determine safe consolidation paths (shared service, shared library, or component merge).
  • Generate actionable consolidation plans with step-by-step guidance for implementation.

Quick Start

Analyze a codebase to identify duplicate domain logic and surface consolidation opportunities.

Frequently Asked Questions about component-common-domain-detection

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

FAQPage Schema
How do I identify duplicate domain logic across multiple components?▼

To identify duplicate domain logic, scan component namespaces for common leaf patterns like notification, audit, and validation to surface overlapping patterns and potential consolidation opportunities.

What is the best way to detect shared domain classes for consolidation?▼

Detecting shared domain classes involves analyzing cross-cutting reuse opportunities by locating shared classes used across multiple components to identify functionality similarity and assess coupling impact.

How do I assess coupling impact before consolidating duplicate code?▼

Assess coupling impact by analyzing functionality similarity across components to determine safe consolidation paths, helping you decide whether to use a shared service, shared library, or component merge.

Can I generate actionable consolidation plans for a multi-service codebase?▼

Yes, you can generate actionable consolidation plans for a multi-service codebase that provide step-by-step implementation guidance for refactoring overlapping patterns and reducing technical debt.

When should I not use a component merge for refactoring duplicate patterns?▼

You should avoid a component merge when coupling impact analysis reveals high dependency risks, indicating that extracting a shared service or shared library is a safer consolidation path for your codebase.

Related Skills

Explore More Software Engineering Skills→
alexjcmalexjcm

component-common-domain-detection

Detect duplicate domain functionality across components and recommend consolidation plans.

Community
Advanced
d-o-hubd-o-hub
11

analysis-dimensions

Detect duplicate code blocks and map architectural structure across a codebase.

Community
Intermediate
RamonsDkaRamonsDka
1

component-common-domain-detection

Detect duplicated domain functionality across components and generate consolidation plans.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

detect-code-smells

Detect code smells and complexity issues in codebases.

Official
Intermediate