tactical-ddd

What problem does it solve?

This skill helps software teams translate domain concepts into clean, expressive code by applying tactical domain-driven design (DDD) principles. It targets reducing coupling between domain and infrastructure, clarifying boundaries for aggregates, and ensuring invariants are preserved across changes. It guides practitioners through isolating domain logic, naming with ubiquitous language, and modeling state transitions with explicit types.

Core Features & Use Cases

• Isolate domain logic from infrastructure to improve testability and readability.
• Model aggregates around invariants to protect consistency across boundaries.
• Use rich domain language with explicit value objects, bounded contexts, and domain events.
• Apply use cases and orchestrate behavior without leaking domain rules into infrastructure.
• Refactor legacy code toward expressive, domain-aligned structures that support evolution.

Quick Start

Example approach: analyze a codebase to identify core domain concepts, map them to aggregates and value objects, and outline explicit invariants. Then draft a plan to replace primitive types with domain-specific value objects and create boundary definitions between domains.