Agent skill · Frontend

component-common-domain-detection

Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before refactoring. Do NOT use for code-level duplication detection (use linters) or dependency analysis (use coupling-analysis).

tech-leads-clubgithub.com/tech-leads-clubGitHub ↗
claude-codecopilotcursorNOASSERTION
Install
npx skills add tech-leads-club/agent-skills --skill component-common-domain-detection --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 17 KB
Bundled scripts: none
Path: packages/skills-catalog/skills/(architecture)/component-common-domain-detection/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 4,983
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Common Domain Component Detection This skill identifies common domain functionality that is duplicated across multiple components and suggests consolidation opportunities to reduce duplication and improve maintainability. ## How to Use ### Quick Start Request analysis of your codebase: - **"Find common domain functionality across components"** - **"Identify duplicate domain logic that should be consolidated"** - **"Detect shared classes used across multiple components"** - **"Analyze consolidation opportunities for common components"** ### Usage Examples **Example 1: Find Common Functionality** ``` User: "Find common domain functionality across components" The skill will: 1. Scan component namespaces for common patterns 2. Detect shared classes used across components 3. Identify duplicate domain logic 4. Analyze coupling impact of consolidation 5. Suggest consolidation opportunities ``` **Example 2: Detect Duplicate Notification Logic** ``` User: "Are there multiple notification components that should be consolidated?" The skill will: 1. Find all components with notification-related names 2. Analyze their functionality and dependencies 3. Calculate coupling impact if consolidated

What's inside
Steps it walks through
  1. How to Use
  2. Quick Start
  3. Usage Examples
  4. Step-by-Step Process
  5. When to Use
  6. Core Concepts
  7. Domain vs Infrastructure Functionality
  8. Common Domain Patterns
  9. Consolidation Approaches
  10. Analysis Process
  11. Phase 1: Identify Common Namespace Patterns
  12. Phase 2: Detect Shared Classes
  13. Phase 3: Analyze Functionality Similarity
  14. Phase 4: Assess Coupling Impact
Ships with 2 files
  • QUICK-REFERENCE.md
  • README.md
More from agent-skills
All skills →
About this skill
What does the component-common-domain-detection skill do?

Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before refactoring. Do NOT use for code-level duplication detection (use linters) or dependency analysis (use coupling-analysis).

How do I install it?

Run `npx skills add tech-leads-club/agent-skills --skill component-common-domain-detection --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going