component-common-domain-detection

Detect duplicated business logic across components using namespace patterns and shared classes.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/rafael-hc/AoPonto-FoodService --skill component-common-domain-detection-rafael-hc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-common-domain-detection
Source: https://github.com/rafael-hc/AoPonto-FoodService/tree/main/.agents/skills/component-common-domain-detection
Command: npx skills add https://github.com/rafael-hc/AoPonto-FoodService --skill component-common-domain-detection-rafael-hc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This skill tackles code duplication by identifying common business logic spread across multiple components, suggesting ways to consolidate them into more maintainable and efficient units.

Core Features & Use Cases

  • Duplicate Logic Detection: Finds common patterns in namespaces and shared classes.
  • Consolidation Strategy: Recommends approaches like shared services, libraries, or component merges.
  • Coupling Analysis: Assesses the impact of consolidation on system coupling.
  • Use Case: You suspect several services are independently implementing similar notification logic. This skill can pinpoint these duplicates, analyze their similarities and differences, and recommend merging them into a single, reusable notification service.

Quick Start

Find common domain functionality across components.

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 find duplicate domain logic spread across multiple components?

To find duplicate domain logic across components, analyze common namespace patterns and shared class usage to pinpoint overlapping business functionality and suggest consolidation opportunities.

What is the best way to consolidate duplicate business logic without increasing coupling?

The best way to consolidate duplicate business logic while managing coupling is to evaluate the coupling impact of proposed merges and recommend strategies like shared services, libraries, or component merges.

How can I distinguish shared domain logic from infrastructure concerns during refactoring?

To distinguish shared domain logic from infrastructure concerns during refactoring, focus your analysis specifically on domain-specific business rules, separating them from general infrastructure code.

Does this component consolidation approach work for identifying duplicated notification logic in services?

Yes, if you suspect several services implement similar notification logic, this approach analyzes their similarities, differences, and coupling impact to recommend merging them into a reusable service.

When should I not use a shared service for code duplication consolidation?

You should reconsider using a shared service for code duplication consolidation when the coupling analysis indicates that merging the components would create tight, undesirable dependencies across your architecture.