dto-creator

Name the entity in your request, such as "create DTO for Vet", and the skill inspects the entity via the Spring MCP server, then generates the DTO with selected fields, constructors, equals/hashCode, and toString. It auto-detects language, JDK, and dependencies to pick the right variant.

The skill decides from project context: Java records when JDK is 16 or higher and Lombok is absent, Lombok annotations when Lombok is on the classpath and requested, and plain classes otherwise. You can override the choice explicitly in your prompt.

Yes, Kotlin projects automatically route to data class generation with val/var constructor parameters, @field: validation annotations, and preserved collection types like MutableSet. Java types are converted to Kotlin equivalents such as Int and String.

Each association offers four options: a separate DTO file, a nested class, reusing an existing DTO, or flat fields like typeId or specialtyIds. Back-reference ManyToOne fields pointing to a parent entity are automatically excluded from selection.

The skill checks for Amplicode MCP tools before starting. If none are available, it delegates to the amplicode-install skill to install the Amplicode IntelliJ plugin and configure the MCP server, then resumes generation.

Yes, when Hibernate Validator or Jakarta Validation is on the classpath, constraints like @NotNull, @Size, and @Pattern are inherited from entity fields by default. You can also add extra constraints or remove inherited ones per field.