domain-model-boundaries-mapper — Claude Code skill for DDD boundaries
domain-model-boundaries-mapper maps domain areas, module ownership, dependencies, and interfaces in a codebase. Useful when untangling a monolith or planning a domain-driven redesign.
MIT 270 installs ★ 64 updated 2026-01-12
npx skills add patricio0312rev/skills --skill domain-model-boundaries-mapper -a claude-codeWhat domain-model-boundaries-mapper does
This skill examines a project's architecture through Domain-Driven Design. It groups code into bounded contexts and describes each area's responsibilities, ownership, terminology, and entities. The resulting domain map shows how those contexts relate to one another, alongside a dependency overview.
It also examines communication between domains. The analysis covers interface contracts, adapters, anti-corruption layers, shared models, and event-based integration. Typical issues include one module querying another module's database directly, or an oversized service handling orders, inventory, payments, and shipping together.
The output includes refactoring suggestions and a staged migration outline, starting with boundary discovery and moving through interface design and decoupling. Extracting separate services is an optional final stage. That distinction matters: the proposed architecture does not automatically require a microservices migration.
What it helps with
- Split a monolith into bounded domain contexts
- Identify overlapping module responsibilities
- Map dependencies between business domains
- Design service interfaces and event contracts
- Replace direct cross-domain database access
Example prompts for the agent
- Review this codebase using DDD and produce a map of its bounded contexts.
- Find modules with overlapping responsibilities and suggest clearer ownership boundaries.
- Inspect service dependencies and propose a refactoring plan for the oversized OrderService.
How to install domain-model-boundaries-mapper
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill domain-model-boundaries-mapper -a claude-code2Manually: put the files in place
~/.claude/skills/domain-model-boundaries-mapper/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/domain-model-boundaries-mapper/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill domain-model-boundaries-mapper -a codex2Manually: put the files in place
.agents/skills/domain-model-boundaries-mapper/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill domain-model-boundaries-mapper -a cursor2Manually: put the files in place
.cursor/skills/domain-model-boundaries-mapper/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install patricio0312rev/skills architecture/domain-model-boundaries-mapper/SKILL.md2Manually: put the files in place
.github/skills/domain-model-boundaries-mapper/SKILL.md1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill domain-model-boundaries-mapper -a gemini-cli2Platform CLI
gemini skills install https://github.com/patricio0312rev/skills --path architecture/domain-model-boundaries-mapperManually: put the files in place
.devin/skills/domain-model-boundaries-mapper/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill domain-model-boundaries-mapper -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about domain-model-boundaries-mapper
How do I install domain-model-boundaries-mapper in Claude Code?
Run npx skills add patricio0312rev/skills --skill domain-model-boundaries-mapper -a claude-code. The installed skill file is located at ~/.claude/skills/domain-model-boundaries-mapper/SKILL.md.
What does domain-model-boundaries-mapper do?
It analyzes a codebase's domain structure and produces bounded-context maps, dependency diagrams, entity definitions, and interface contracts. It also identifies coupling problems and suggests architectural changes.
Can this skill help plan a microservices migration?
Yes. It outlines domain separation, API and adapter design, and the extraction of independent services. Service extraction is an optional stage rather than a mandatory outcome.
Source text
SKILL.md · MIT
---
name: domain-model-boundaries-mapper
description: Identifies domain modules, ownership boundaries, dependencies, and interfaces using Domain-Driven Design principles. Provides domain maps, bounded contexts, refactor recommendations. Use for "DDD", "domain modeling", "bounded contexts", or "service boundaries".
---
# Domain Model & Boundaries Mapper
Map domain boundaries and ownership using Domain-Driven Design.
## Domain Map Template
```markdown
# Domain Map: E-Commerce Platform
## Bounded Contexts
### 1. Customer Management
**Core Domain:** User accounts, profiles, preferences
**Owner:** Customer Team
**Ubiquitous Language:**
- Customer: Registered user with account
- Profile: Customer personal information
- Preferences: User settings and choices
**Entities:**
- Customer (id, email, name)
- Address (id, customer_id, street, city)
- PaymentMethod (id, customer_id, type, token)
**Bounded Context Diagram:**
```
┌─────────────────────────────┐
│ Customer Management │
│ ┌─────────┐ ┌──────────┐ │
│ │Customer │ │ Address │ │
│ └─────────┘ └──────────┘ │
│ ┌─────────────────────┐ │
│ │ Payment Method │ │
│ └─────────────────────┘ │
└─────────────────────────────┘
```
### 2. Order Management
**Core Domain:** Order processing, fulfillment
**Owner:** Orders Team
**Ubiquitous Language:**
- Order: Purchase request with line items
- LineItem: Product quantity in order
- Fulfillment: Physical delivery of order
**Entities:**
- Order (id, customer_id, status, total)
- LineItem (id, order_id, product_id, quantity)
- Shipment (id, order_id, tracking_number)
### 3. Product Catalog
**Core Domain:** Product information, inventory
**Owner:** Catalog Team
**Ubiquitous Language:**
- Product: Sellable item
- SKU: Stock keeping unit
- Inventory: Available stock
**Entities:**
- Product (id, name, price, description)
- Inventory (sku, quantity, warehouse_id)
## Context Relationships
```
Customer Management ──────▶ Order Management
(customer_id)
Product Catalog ──────▶ Order Management
(product_id)
Order Management ──────▶ Fulfillment
(order events)
````
## Anti-Corruption Layers
### Order Management → Customer Management
**Problem:** Orders need customer data but shouldn't depend on Customer domain model
**Solution:** Customer Adapter
```typescript
// Order domain's view of customer
interface CustomerForOrder {
id: string;
shippingAddress: Address;
billingAddress: Address;
}
// Adapter translates Customer domain to Order domain
class CustomerAdapter {
async getCustomerForOrder(customerId: string): Promise<CustomerForOrder> {
const customer = await customerService.getCustomer(customerId);
return {
id: customer.id,
shippingAddress: this.toOrderAddress(customer.defaultShippingAddress),
billingAddress: this.toOrderAddress(customer.defaultBillingAddress),
};
}
}
````
## Dependency Map
```
┌──────────────┐
│ Customer │
└──────┬───────┘
│
▼
┌──────────────┐ ┌────────────┐
│ Orders │─────▶│ Products │
└──────┬───────┘ └────────────┘
│
▼
┌──────────────┐
│ Fulfillment │
└──────────────┘
```
**Dependency Rules:**
- Customer has no dependencies
- Orders depends on Customer (read) and Products (read)
- Fulfillment depends on Orders (events)
## Interface Contracts
### Customer Management → Orders
```typescript
// Public interface exposed by Customer domain
interface CustomerService {
getCustomer(id: string): Promise<Customer>;
getCustomerAddresses(id: string): Promise<Address[]>;
}
// Events published
interface CustomerUpdated {
customerId: string;
email: string;
name: string;
}
```
### Product Catalog → Orders
```typescript
interface ProductService {
getProduct(id: string): Promise<Product>;
checkAvailability(sku: string, quantity: number): Promise<boolean>;
reserveInventory(items: ReservationRequest[]): Promise<Reservation>;
}
```
## Refactor Recommendations
### Problem 1: Tight Coupling
**Current:** Orders directly queries Customer database
**Issue:** Breaks bounded context, creates coupling
**Recommendation:** Use Customer API instead
```typescript
// ❌ Before: Direct database access
const customer = await db.customers.findById(customerId);
// ✅ After: API call through adapter
const customer = await customerAdapter.getCustomerForOrder(customerId);
```
### Problem 2: Shared Models
**Current:** Same `User` model used across contexts
**Issue:** Changes in one context affect others
**Recommendation:** Separate models per context
```typescript
// Customer context
interface Customer {
id: string;
email: string;
profile: CustomerProfile;
preferences: CustomerPreferences;
}
// Order context (different model!)
interface OrderCustomer {
id: string;
shippingAddress: Address;
billingAddress: Address;
}
```
### Problem 3: God Service
**Current:** `OrderService` handles orders, inventory, payments, shipping
**Issue:** Single service owns too much
**Recommendation:** Extract bounded contexts
- OrderService: Order lifecycle
- InventoryService: Stock management
- PaymentService: Payment processing
- FulfillmentService: Shipping
## Strategic Design Patterns
### Pattern 1: Shared Kernel
**When:** Two contexts must share some code
**Example:** Common value objects (Money, Address)
```typescript
// Shared kernel (minimal!)
class Money {
constructor(public amount: number, public currency: string) {}
}
```
### Pattern 2: Customer/Supplier
**When:** One context depends on another
**Example:** Orders (customer) depends on Products (supplier)
- Supplier defines interface
- Customer adapts to their needs
### Pattern 3: Published Language
**When:** Many contexts need same data
**Example:** Product events
```typescript
interface ProductCreated {
productId: string;
name: string;
price: Money;
publishedAt: Date;
}
```
## Migration Strategy
### Phase 1: Identify Boundaries
- [ ] Map existing code to domains
- [ ] Identify coupling points
- [ ] Document dependencies
### Phase 2: Define Interfaces
- [ ] Design APIs between contexts
- [ ] Create adapter layers
- [ ] Define event contracts
### Phase 3: Decouple
- [ ] Replace direct DB access with APIs
- [ ] Introduce anti-corruption layers
- [ ] Separate models per context
### Phase 4: Extract Services (optional)
- [ ] Move contexts to separate services
- [ ] Implement API gateways
- [ ] Set up event bus
## Best Practices
1. **Ubiquitous language**: Same terms in code and domain
2. **Bounded contexts**: Clear boundaries, separate models
3. **Context maps**: Document relationships
4. **Anti-corruption layers**: Protect domain integrity
5. **Event-driven**: Loose coupling via events
6. **Separate databases**: Context owns its data
## Output Checklist
- [ ] Bounded contexts identified (3-7)
- [ ] Core domain vs supporting domains
- [ ] Ubiquitous language defined per context
- [ ] Entity/aggregate definitions
- [ ] Context relationship diagram
- [ ] Dependency map
- [ ] Interface contracts defined
- [ ] Anti-corruption layers designed
- [ ] Refactor recommendations
- [ ] Migration strategy
© patricio0312rev · MIT · patricio0312rev/skills