domain-analysis

Identify subdomains and map bounded contexts across codebases.

59|14|Updated Mar 10, 2026

Search Tags:#domain-driven-design #cohesion #bounded-context #subdomain #ddd-patterns #linguistic-boundary

Ready to run

npx skills add https://github.com/guilhermemarketing/esc-skills --skill domain-analysis-guilhermemarketing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-analysis
Source: https://github.com/guilhermemarketing/esc-skills/tree/main/skills/domain-analysis
Command: npx skills add https://github.com/guilhermemarketing/esc-skills --skill domain-analysis-guilhermemarketing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain boundaries often confuse teams; this skill helps identify subdomains and map bounded contexts to align language and architecture.

Core Features & Use Cases

Extract business concepts (entities, services, use cases) and group them by ubiquitous language
Identify subdomains and classify as Core, Supporting, or Generic, then propose bounded contexts
Assess cohesion and detect cross-domain coupling to guide refactoring and integration

Quick Start

Provide a codebase or repository and I will output subdomain maps and bounded contexts.

Frequently Asked Questions about domain-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify subdomains and bounded contexts in a codebase?▼

To identify subdomains and bounded contexts, you provide a codebase to extract business concepts, group them by ubiquitous language, and classify them as Core, Supporting, or Generic. This produces subdomain maps and proposed linguistic boundaries.

What is the best way to map bounded contexts from existing source code?▼

Mapping bounded contexts from source code involves analyzing business vocabulary to group entities and use cases. The process assesses cohesion and detects cross-domain coupling to output integration patterns and clear linguistic boundaries.

Can I use domain-driven design analysis for both monoliths and microservices?▼

Yes, domain-driven design analysis applies to any language and architecture, from monoliths to microservices. It evaluates cross-domain coupling and cohesion scores to guide refactoring regardless of the architectural style.

Do I need ubiquitous language to analyze domain boundaries?▼

Yes, clear business vocabulary or ubiquitous language is required to analyze domain boundaries. The analysis relies on this linguistic input to accurately group business concepts and define cohesive bounded contexts.

How does subdomain classification improve codebase architecture?▼

Subdomain classification improves architecture by categorizing areas as Core, Supporting, or Generic. This highlights cross-domain coupling and provides integration patterns to guide targeted refactoring and align language with architecture.

Why does domain boundary confusion occur and how is it resolved?▼

Domain boundary confusion occurs when teams lack clear linguistic separation. It is resolved by mapping subdomains and bounded contexts using ubiquitous language, which produces cohesion scores and cross-domain refactoring recommendations.