Java DDD Architecture

Activation Guard

Before applying this skill, check the project's main instruction file such as AGENTS.md, CLAUDE.md, or equivalent. Use it only when that file explicitly states the project uses DDD or Domain-Driven Design.

For an active architecture/design review, also use java-solid-review for material cross-cutting design risks. Its general heuristics must not override project-specific DDD decisions.

Project Guidance

Follow the DDD rules in the project's own instruction files and domain docs.

• Preserve clear boundaries and responsibilities between domain concepts, application services, and infrastructure concerns.
• Ask for clarification before changing aggregates, entities, value objects, repositories, domain services, bounded-context language, or domain invariants when rules are missing or unclear.
• Prefer anemic domain models with behavior primarily in services unless there is a strong reason to keep logic on the entity itself.

Repository Contracts

When adding or refactoring a domain repository, read repository boundaries.