component-common-domain-detection

What problem does it solve? Large codebases often accumulate duplicate business logic—notification, audit, validation, and formatting code copied across multiple components. This duplication increases maintenance cost and inconsistency, but consolidating blindly can create dangerous coupling bottlenecks. This Skill finds the duplication and tells you whether consolidating it is safe. ## Core Features & Use Cases - Namespace Pattern Detection: Scans component namespaces for common leaf-node patterns like *.notification, *.audit, and *.validation to group similar components. - Shared Class Detection: Identifies classes imported by multiple components and classifies them as domain logic versus infrastructure concerns. - Coupling Impact Analysis: Calculates afferent coupling (CA) before and after proposed consolidation to verify it does not create a bottleneck. - Consolidation Recommendations: Suggests the right approach—shared service, shared library, or component merge—based on change frequency and complexity. - Use Case: Ask whether three notification components in customer, ticket, and survey services should be merged, and receive a feasibility verdict with a step-by-step consolidation plan. ## Quick Start Ask the agent to find common domain functionality across components and analyze consolidation opportunities in your codebase.