nw-ddd-strategic
Strategic DDD — bounded context discovery, context mapping patterns, subdomain classification, ubiquitous language, and organizational alignment
Install / Use
npx skills add nWave-ai/nWave --skill nw-ddd-strategicInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of nw-ddd-strategic
nw-ddd-strategic scores 89/100 on our quality scale, 1724th of 4,702 Development & Engineering skills we index (top 37%).
Its SKILL.md is 6.4 KB long, well organised into 15 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
It has 617 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so nw-ddd-strategic is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
nw-ddd-strategic compared with similar skills
All 4 of these similar skills score higher than nw-ddd-strategic; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| nw-ddd-strategic (this skill)by nWave-ai | 89 | 617 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.7k | today | MCP Server |
Frequently asked questions
- How do I install nw-ddd-strategic?
- Run
npx skills add nWave-ai/nWave --skill nw-ddd-strategic. The install tabs above show the steps for each supported agent. - Which AI agents does nw-ddd-strategic work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is nw-ddd-strategic safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is nw-ddd-strategic still maintained?
- The repository was last updated about 2 months ago, so nw-ddd-strategic is actively maintained.
Skill content
View source on GitHubname: nw-ddd-strategic description: Strategic DDD — bounded context discovery, context mapping patterns, subdomain classification, ubiquitous language, and organizational alignment user-invocable: false disable-model-invocation: true
Strategic DDD
Domain discovery and boundary definition at the organizational level. Strategic DDD answers: "Where are the boundaries?" and "How do contexts relate?"
Subdomain Classification
Subdomains exist in the problem space. Classify before modeling.
| Type | Competitive advantage | Build or buy | DDD investment | Staffing | |------|----------------------|--------------|----------------|----------| | Core | Yes, unique differentiator | Build in-house | Full strategic + tactical | Senior talent | | Supporting | No, enables core | Build (simplified) or outsource | Pragmatic tactical | Mid-level | | Generic | No, commodity | Buy/integrate (Stripe, Auth0) | Minimal/none | Junior/integration |
Decision heuristic: If two competitors solve this the same way, it's Generic. If your approach gives you an edge, it's Core. Everything else is Supporting.
Bounded Context Discovery
A bounded context is a software boundary within which a model is consistent. Different from subdomains (problem-space). They should align but are independent concepts.
Discovery Techniques
Language divergence (primary signal): When the same word means different things to different groups, you've found a boundary. "Account" in billing vs. "Account" in identity. "Product" in catalog vs. "Product" in inventory.
Organizational structure: Teams that communicate frequently often share a context. Teams with formal handoffs often have separate contexts. Conway's Law applies.
Consistency requirements: Where true invariants must be maintained transactionally defines aggregate boundaries, which cluster into contexts.
EventStorming Big Picture: Domain events placed on timeline. When events cluster into distinct swimlanes with different actors and vocabulary, those are context candidates.
Domain Storytelling: Actors perform activities on work objects. When actors, activities, or work objects change meaning, you've crossed a boundary.
Boundary Validation Checklist
- [ ] Each context has its own ubiquitous language (no term means two things)
- [ ] One team owns one context (no shared ownership)
- [ ] Context is independently deployable (no mandatory co-deployment)
- [ ] Internal model changes don't ripple to other contexts
- [ ] Data that crosses boundaries is explicitly mapped (no implicit sharing)
Common Mistakes
- Context = microservice: A context may contain multiple services; a service may handle a subdomain within a larger context
- Too large: Conflicting models coexist, vocabulary is ambiguous -- split
- Too small: Excessive cross-context communication, simple operations need sagas -- merge
- Database-first: Sharing a database between contexts couples their models implicitly
Context Mapping Patterns
Nine patterns describing how bounded contexts relate. Draw the context map before writing code.
Mutually Dependent
Partnership: Two contexts evolve together. Both teams coordinate releases. Use when: genuinely reciprocal dependency, tight collaboration feasible. Risk: high coordination cost.
Shared Kernel: Small shared model subset both contexts depend on. Must be small, explicitly versioned, jointly owned. Changes require agreement from both teams.
Upstream/Downstream
Customer-Supplier: Upstream serves downstream's needs. Downstream negotiates what upstream provides. Structured relationship with explicit API contracts.
Conformist: Downstream adopts upstream's model as-is. No negotiation. Use when: integration simplicity outweighs design freedom, or upstream won't accommodate.
Anti-Corruption Layer (ACL): Downstream creates a translation layer to isolate its model from upstream's. Essential for: legacy integration, poor upstream models, protecting domain purity.
Open Host Service (OHS): Upstream provides a well-defined API for multiple downstream consumers. Standardized protocol (REST, gRPC, GraphQL).
Published Language: Shared schema or format for inter-context communication. Examples: iCalendar, vCard, JSON Schema, Protocol Buffers.
Independent
Separate Ways: No integration. Contexts have no meaningful dependency. Duplication is acceptable when coupling cost exceeds duplication cost.
Big Ball of Mud: Recognition pattern only. Demarcate and quarantine legacy systems. Draw a boundary around them, communicate through ACL.
Selection Heuristic
Do the teams need to coordinate releases?
YES -> Do both depend on each other equally?
YES -> Partnership (if feasible) or Shared Kernel (if small overlap)
NO -> Customer-Supplier (negotiate API)
NO -> Is upstream model acceptable?
YES -> Conformist (adopt as-is)
NO -> Anti-Corruption Layer (translate)
Independent? -> Separate Ways
Legacy mess? -> Big Ball of Mud + ACL
Ubiquitous Language
A rigorous vocabulary shared between developers and domain experts, scoped per bounded context.
Rules
- Domain terms in code: class names, method names, variable names reflect domain language
- Same term, different context: "Order" in Sales vs. "Order" in Fulfillment are different concepts -- this is expected and healthy
- When the model is hard to express in code, the language needs refinement
- Resolve conflicts immediately: if developers and domain experts use different words for the same concept, pick one and enforce it
Building the Language
- Maintain a glossary per bounded context (not per system)
- Review glossary during modeling sessions
- When new terms emerge, add them; when terms change, update code
- Code review should catch language violations ("this variable should be called X, not Y")
Context Map Visualization
Use Mermaid flowchart for context maps:
flowchart LR
subgraph Core
OrderCtx[Order Context]
CatalogCtx[Catalog Context]
end
subgraph Supporting
NotifCtx[Notification Context]
end
subgraph Generic
PaymentCtx[Payment Context]
AuthCtx[Identity Context]
end
OrderCtx -->|Customer-Supplier| CatalogCtx
OrderCtx -->|ACL| PaymentCtx
OrderCtx -->|OHS| NotifCtx
CatalogCtx -.->|Conformist| AuthCtx
Label every arrow with the context mapping pattern. Core contexts in the center.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.7k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
