domain-identification-grouping
Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).
npx skills add tech-leads-club/agent-skills --skill domain-identification-grouping --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
This skill groups architectural components into logical business domains to prepare for creating domain services in a service-based architecture.
How it works
- It analyzes component responsibilities and relationships to identify business domains.
- It assigns components to appropriate domains and creates domain diagrams.
- It suggests namespace refactoring to align namespaces with identified domains.
- It validates groupings and can create a domain map and domain inventory.
- It outputs a Domain Identification section, a Component Domain Assignment table, a Namespace Refactoring Plan, and a Domain Map visualization, showing domain structures and relationships.
When to use it
Use when asked to group components into logical domains, identify component domains for a service-based architecture, or create domain groupings from components, and to analyze which components belong to which domains.
What it can touch
- No specific tool interactions are listed beyond suggested namespace refactoring; the plan includes updating namespace declarations, imports, and directory structures in the general workflow.
Caveats
- The skill emphasizes grouping existing components into domains and explicitly cautions against identifying new domains (use domain-analysis) or analyzing coupling (use coupling-analysis).
# Domain Identification and Grouping This skill groups architectural components into logical domains (business areas) to prepare for creating domain services in a service-based architecture. ## How to Use ### Quick Start Request analysis of your codebase: - **"Group components into logical domains"** - **"Identify component domains for service-based architecture"** - **"Create domain groupings from components"** - **"Analyze which components belong to which domains"** ### Usage Examples **Example 1: Domain Identification** ``` User: "Group components into logical domains" The skill will: 1. Analyze component responsibilities and relationships 2. Identify business domains based on functionality 3. Group components into domains 4. Create domain diagrams 5. Suggest namespace refactoring for domain alignment ``` **Example 2: Domain Analysis** ``` User: "Which domain should the billing components belong to?" The skill will: 1. Analyze billing component functionality 2. Check relationships with other components 3. Identify appropriate domain (e.g., Customer or Financial) 4. Recommend domain assignment ``` **Example 3: Domain Refactoring** ``` User: "What namespace refactoring is needed t
- How to Use
- Quick Start
- Usage Examples
- Step-by-Step Process
- When to Use
- Core Concepts
- Domain Definition
- Component Domain Relationship
- Domain Manifestation
- Analysis Process
- Phase 1: Identify Business Domains
- Phase 2: Group Components into Domains
- Phase 3: Validate Domain Groupings
- Phase 4: Refactor Namespaces for Domain Alignment
What does the domain-identification-grouping skill do?
Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).
How do I install it?
Run `npx skills add tech-leads-club/agent-skills --skill domain-identification-grouping --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.