Java DDD Project

Use this skill to make Java changes that fit an existing Maven or Gradle project with Spring Boot and clear domain, application, infrastructure, and interface boundaries.

Core Rules

• Inspect the repository before changing it: pom.xml, build.gradle, src/main/, src/test/, CI files, AGENTS.md, and local docs.
• Apply these conventions only when they match the repo or the user asks to standardize on them. Preserve stronger local conventions.
• Keep changes scoped to the request. Do not turn a bug fix into a framework migration.
• Use project-pinned tooling (mvnw or gradlew) when available.
• Keep dependency changes coherent: update dependency management files (pom.xml or build.gradle) and lockfiles/dependency verification configs if present.
• Keep dependency direction inward: domain code must not import infrastructure, interface, framework (e.g., Spring Boot), ORM (e.g., Hibernate/JPA), or serialization libraries (e.g., Jackson).
• Prefer validated @ConfigurationProperties objects over scattered @Value or environment reads; inject configuration properties into application or infrastructure code.
• Validate with the repo's real checks and state any skipped checks or inferred conventions in the final response.

Workflow