What problem does it solve? When adding code to a DDD hexagonal (ports & adapters) Spring Boot codebase, developers struggle to decide which layer a new class belongs in, how to design ports, and how to keep bounded contexts decoupled. This Skill encodes the project's architecture rules so every new class, port, aggregate, and context follows the same structure. ## Core Features & Use Cases - Layer and dependency rules: Defines the domain/application/infrastructure/presentation four-layer structure, allowed dependency directions, and the rule that the domain layer has zero framework dependencies. - Bounded context guidance: Documents the six contexts (address, job, dwelling, infra, support, recommendation), the shared kernel value objects, and criteria for creating new contexts. - Port and aggregate design: Specifies out-port placement in domain/port, the no-in-port convention (application Service as the public entry point), aggregate ID-only references, and value object invariants. - Use Case: When adding a new JPA adapter or cache port, consult this Skill to place the interface in domain/port, implement it in infrastructure, and wire the correct transaction manager. ## Quick Start Use the architecture-conventions skill to decide which layer and package a new dwelling score cache adapter belongs in.
