nw-ddd-tactical
Tactical DDD — aggregate design rules, entities, value objects, domain events, repositories, domain services, and anti-pattern detection
Install / Use
npx skills add nWave-ai/nWave --skill nw-ddd-tacticalInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of nw-ddd-tactical
nw-ddd-tactical scores 83/100 on our quality scale, 3204th of 4,702 Development & Engineering skills we index.
Its SKILL.md is 7.0 KB long, well organised into 14 sections and no 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-tactical is actively maintained.
- Our last check on 2026-11-07 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-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
nw-ddd-tactical compared with similar skills
All 4 of these similar skills score higher than nw-ddd-tactical; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| nw-ddd-tactical (this skill)by nWave-ai | 83 | 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 |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
Frequently asked questions
- How do I install nw-ddd-tactical?
- Run
npx skills add nWave-ai/nWave --skill nw-ddd-tactical. The install tabs above show the steps for each supported agent. - Which AI agents does nw-ddd-tactical 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-tactical 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-tactical still maintained?
- The repository was last updated about 2 months ago, so nw-ddd-tactical is actively maintained.
Skill content
View source on GitHubname: nw-ddd-tactical description: Tactical DDD — aggregate design rules, entities, value objects, domain events, repositories, domain services, and anti-pattern detection user-invocable: false disable-model-invocation: true
Tactical DDD
Implementation patterns within a bounded context. Tactical DDD answers: "How do we structure the domain model?"
Aggregates
An aggregate is a consistency boundary -- a cluster of domain objects that must be transactionally consistent.
Vernon's Four Design Rules
-
Model true invariants in consistency boundaries: Only include elements that MUST be consistent within the same transaction. If two entities don't share an invariant, they belong in separate aggregates.
-
Design small aggregates: ~70% of aggregates contain only a root entity with value-typed properties. Large aggregates create concurrency contention, scalability failures, and memory pressure.
-
Reference other aggregates by identity: Use
ProductIdnotProduct. Direct object references create accidental cross-aggregate transactions and prevent independent scaling. -
Use eventual consistency outside the boundary: Domain events communicate across aggregates. One transaction = one aggregate. If you need to update two aggregates "atomically," reconsider your boundaries.
Aggregate Design Checklist
- [ ] Contains only elements sharing true invariants
- [ ] Root entity controls all access (no direct child manipulation)
- [ ] External references by ID only (no object graphs)
- [ ] Small enough for single-transaction performance
- [ ] Command produces events (in event-sourced systems) or mutates state (in traditional)
- [ ] Business rules validated in command handling, not in persistence layer
Common Aggregate Smells
| Smell | Signal | Fix | |-------|--------|-----| | God Aggregate | >5 entities, frequent concurrency conflicts | Split by invariant analysis | | Anemic Aggregate | All logic in services, aggregate = data bag | Move business rules into aggregate methods | | Cross-Aggregate Transaction | Two aggregates modified in one DB transaction | Use domain events + eventual consistency | | Deep Nesting | Aggregate root -> entity -> entity -> value | Flatten; promote nested entities to own aggregates | | Missing Aggregate | Business rules scattered in application services | Identify invariant cluster, create aggregate |
Entities
Objects with identity that persists across state changes. An entity is the "same" entity even when all its attributes change (a person who changes name, address, and job is still the same person).
Design rules: Identity is assigned once and never changes | Equality by identity, not attributes | Track lifecycle (created, modified, archived) | Place business rules that depend on identity here
Value Objects
Objects defined by their attributes, not identity. Two value objects with the same attributes are interchangeable.
Design rules:
- Immutable: Never modify; create new instances
- Self-validating: Constructor rejects invalid state. If a
Moneyobject exists, it has a valid amount and currency - Side-effect-free behavior: Methods return new values, don't mutate
- Structural equality: Compare by attributes, not reference
Examples: Money(amount, currency) | Email(address) | DateRange(start, end) | Address(street, city, zip, country) | Temperature(value, unit)
Context sensitivity: Whether something is Entity or Value Object depends on bounded context. Address is a VO in e-commerce (shipping destination) but an Entity in utility billing (service location with lifecycle).
Domain Events
Represent something that happened in the domain. Always past tense.
Naming Convention
| Correct (past tense) | Wrong (imperative) | |----------------------|-------------------| | OrderPlaced | PlaceOrder (that's a command) | | PaymentReceived | ReceivePayment | | UserRegistered | RegisterUser | | InventoryReserved | ReserveInventory |
Event Design Guidelines
- Self-contained: Include all data needed to understand what happened
- Domain language: Business terms, not technical jargon
- One fact per event:
OrderConfirmednotOrderStatusChanged - No behavior: Events carry data only
- Granularity matters: Too coarse (OrderUpdated) loses meaning; too fine (OrderFieldChanged) is a generic audit log
Event Categories
Domain events (in-process): Within a bounded context, dispatched via mediator. Collected during command handling, dispatched before/after commit.
Integration events (distributed): Cross bounded-context via message brokers. Always asynchronous. Published only after successful persistence. May use different schema than domain events (translated at boundary).
Repositories
One repository per aggregate (not per entity). Interface defined in domain layer, implementation in infrastructure.
Collection-oriented: add/remove/find -- repository tracks changes (Unit of Work pattern). Natural for ORMs.
Persistence-oriented: explicit save/load -- caller manages lifecycle. Natural for document DBs and event-sourced systems.
Rules: Never expose persistence details (SQL, JSON) to domain | Return domain objects, not DTOs | Query methods use domain language (findActiveOrders, not findByStatusEquals)
Domain Services
Stateless operations that span multiple aggregates or don't naturally belong to any single entity.
When to use: Operation involves multiple aggregates | Logic doesn't belong to any entity | Named using ubiquitous language
Danger: Overuse creates anemic domain models. First try to place the behavior on an entity or aggregate. Domain service is the last resort for truly cross-aggregate logic.
| Domain Service | Application Service | |---------------|-------------------| | Domain logic (rules, calculations) | Orchestration (transaction, security, events) | | Domain types only | Domain + infrastructure ports | | Domain layer | Application layer | | TransferFunds, CalculateDiscount | PlaceOrderHandler, RegisterUserUseCase |
Anti-Pattern Detection
When analyzing existing code, look for these patterns:
| Anti-Pattern | Code Signal | Recommendation |
|-------------|-------------|----------------|
| Anemic Domain Model | Entities = data classes, services contain all if logic | Move business rules to entities/aggregates |
| Primitive Obsession | String email, double amount, int quantity | Create value objects: Email, Money, Quantity |
| Database-Driven Design | Entities mirror DB tables 1:1, foreign keys as navigation | Model domain first, map to persistence second |
| Missing Boundaries | Single model used by all features, vocabulary conflicts | Identify contexts via language divergence |
| Logic in Wrong Layer | Business rules in controllers/handlers | Push down to domain objects |
| Service Bloat | Service class with 20+ methods | Split by use case, push logic to aggregates |
| Event as RPC | Event handler returns result that caller depends on | Events are fire-and-forget; use command for request-response |
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.
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
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.
