domain-decomposition-api-design-advisor

Decompose business requirements by analyzing domain boundaries to ensure low coupling and high cohesion. This skill maps complex logic into well-defined bounded contexts and technical boundaries for Kotlin and Spring architectures before implementation begins.

You need domain-driven design when adopting microservices or starting new features to prevent poorly defined system boundaries. It provides a structured framework to determine whether a module, bounded context, or separate service is the most appropriate architectural choice.

The best way to establish API contracts is through contract-first design, which builds API and event schemas based on consumer needs rather than internal data structures. This ensures consistent API contracts and clear ownership across bounded contexts.

Model architectural tradeoffs by generating formal architectural designs that include ADR-quality reasoning and explicit consistency modeling. This ensures clear ownership and consistent API contracts are validated before any implementation begins.

This approach applies to the architectural design phase of Kotlin and Spring-based systems to ensure clear ownership. You can use it when starting a new feature to determine whether a module, bounded context, or separate service is the most appropriate architectural choice.