component-common-domain-detection

Detect duplicate domain functionality across components and recommend consolidation plans.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/alexjcm/agent-skillset --skill component-common-domain-detection-alexjcm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-common-domain-detection
Source: https://github.com/alexjcm/agent-skillset/tree/main/skills/arquitecture/component-common-domain-detection
Command: npx skills add https://github.com/alexjcm/agent-skillset --skill component-common-domain-detection-alexjcm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and consolidates duplicate domain functionality across components to reduce duplication and improve maintainability within a codebase.

Core Features & Use Cases

  • Detect common namespace patterns across components (e.g., *.notification, *.audit, *.validation).
  • Discover shared classes used by multiple components and assess their applicability for consolidation.
  • Analyze functionality similarity and calculate coupling impact to determine safe consolidation paths.
  • Provide actionable consolidation plans (shared service, shared library, or component merge) with a prioritized roadmap.
  • Support framework-agnostic guidance and language-specific notes documented in the included references.

Quick Start

Analyze common domain patterns and shared classes across the repository to 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 detect duplicate domain logic across components in my codebase?

Duplicate domain logic detection analyzes component namespaces and shared classes to surface common patterns, assessing functionality similarity and coupling impact to identify safe consolidation opportunities.

What is the best way to consolidate shared classes used by multiple components?

Consolidating shared classes involves analyzing functionality similarity and calculating coupling impact across modules to recommend a shared-service, shared-library, or component merge approach with a prioritized roadmap.

How does namespace pattern analysis work for finding duplicate code?

Namespace pattern analysis scans component namespaces for common domain patterns like notification, audit, or validation to surface duplicate domain functionality and calculate coupling impact across modules.

When do I need domain consolidation plans for my codebase?

Domain consolidation plans are needed when duplicate domain functionality across components increases maintenance burden, requiring structured guidance with prioritized roadmaps and output templates for shared-service or merge approaches.

Can I use this approach for framework-agnostic code analysis?

Framework-agnostic guidance is supported for domain consolidation, with language-specific notes documented in references to analyze functionality similarity and calculate coupling impact across diverse codebases.

What are the limitations of coupling impact analysis for domain consolidation?

Coupling impact analysis limitations depend on the accuracy of namespace pattern detection and shared class discovery, requiring careful assessment of functionality similarity before executing any consolidation plans.