component-common-domain-detection

Detect duplicate domain logic across components and propose consolidation approaches.

5.0k|454|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/tech-leads-club/agent-skills --skill component-common-domain-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-common-domain-detection
Source: https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/%28architecture%29/component-common-domain-detection
Command: npx skills add https://github.com/tech-leads-club/agent-skills --skill component-common-domain-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies and consolidates duplicate domain logic across components and proposes consolidation opportunities to reduce duplication and improve maintainability.

Core Features & Use Cases

  • Namespace pattern detection: locate components with shared leaf names such as notification, audit, or validation.
  • Shared class detection: identify commonly used domain classes across components.
  • Feasibility analysis: assess coupling impact and suggest consolidation approaches (shared service, shared library, or component merge).
  • Consolidation planning: provide step-by-step plans and risk mitigation.

Quick Start

Ask the skill to find common domain components, detect duplicate logic, or analyze consolidation opportunities. For example: "Find common domain functionality across components" or "Identify duplicate domain logic that should be consolidated."

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 components for consolidation?

To identify duplicate domain logic, analyze component namespaces for shared leaf names like notification or audit, and detect commonly used shared classes across components to spot consolidation opportunities.

What is the best way to plan a safe migration for consolidating shared domain classes?

Plan safe migration by assessing coupling impact and feasibility first, then choosing a consolidation approach like a shared service, shared library, or component merge, followed by step-by-step rollout and risk mitigation.

Can I use namespace pattern detection for large enterprise codebases?

Yes, namespace pattern detection works for a range of codebases from small repositories to large enterprise projects, analyzing component namespaces and shared classes to propose safe consolidation approaches.

When should I choose a shared service over a shared library for component consolidation?

Choose a shared service, shared library, or component merge based on the feasibility analysis, which assesses the coupling impact of the duplicate domain logic to recommend the safest consolidation approach.

Why does duplicate domain logic persist across components with similar namespace patterns?

Duplicate domain logic persists because components with shared leaf names like validation or audit often implement similar functionality independently, requiring namespace and shared class analysis to identify and consolidate.