java-dto-converter

Generate DTO templates and MapStruct converters for Spring Boot projects.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/cooker/wx-apartment-ledger --skill java-dto-converter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java-dto-converter
Source: https://github.com/cooker/wx-apartment-ledger/tree/main/.agents/skills/java-dto-converter
Command: npx skills add https://github.com/cooker/wx-apartment-ledger --skill java-dto-converter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and implement standardized DTOs and MapStruct converters for Spring Boot layered projects to ensure consistency and maintainability across modules.

Core Features & Use Cases

  • DTO naming conventions for requests, responses, and generic wrappers (IdResp, PageReq, PageResult, etc.)
  • MapStruct converter templates and after-mapping hooks to centralize mapping logic
  • Examples and templates for common modules like policy, task, and api responses
  • Use Case: standardize data transfer models and reduce boilerplate across services

Quick Start

Create a sample PolicyCreateReq and map it to an entity using PolicyConverter.

Frequently Asked Questions about java-dto-converter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate DTOs and MapStruct converters for a Spring Boot project?

Standardized DTOs in Spring Boot use naming conventions for requests, responses, and generic wrappers like IdResp, PageReq, and PageResult to ensure consistent data transfer models across modules.

What's the best way to standardize DTO naming conventions for requests and responses in Spring Boot?

Standardized DTOs in Spring Boot use naming conventions for requests, responses, and generic wrappers like IdResp, PageReq, and PageResult to ensure consistent data transfer models across modules.

How do I centralize MapStruct mapping logic across different modules?

MapStruct handles robust merge and update patterns by providing updateEntity methods and after-mapping hooks within converter templates to apply partial updates to existing entities.

Can I use MapStruct to handle entity merge and update patterns in layered architectures?

MapStruct handles robust merge and update patterns by providing updateEntity methods and after-mapping hooks within converter templates to apply partial updates to existing entities.

Does this approach support adding validation annotations and OpenAPI schemas to data transfer objects?

This approach supports adding validation annotations and OpenAPI schemas directly to DTO templates to ensure data integrity and API documentation consistency across Spring Boot services.