What naming conventions does it enforce?

It uses a standardized naming convention of XCmd for command inputs, XQuery for query inputs, and XResult or VM for output objects to maintain clarity.

What architecture pattern does this skill use?

It follows the Command-Query Separation (CQS) pattern, creating separate classes for write (Command) and read (Query) operations to improve maintainability and performance.

Does it include mapper generation?

Yes, it generates Component-based Mappers to safely transform internal database entities into external-facing ViewModels or DTOs.

Can I use this for existing Spring Boot projects?

Absolutely. The skill is designed to align with standard Spring Boot package structures and can be used to refactor or expand existing service layers.

Does it handle database transactions automatically?

Yes, it automatically applies the @Transactional annotation to write services and @Transactional(readOnly = true) to read services to ensure data integrity.

Spring Service Creator

Name: Spring Service Creator
Author: sivaprasadreddy

bysivaprasadreddy

•

Desarrollo de API

Generates enterprise-ready Spring Boot service layers using Command-Query Separation (CQS) patterns and transactional best practices.

Acerca de

The Spring Service Creator skill streamlines Java backend development by automating the generation of high-quality service classes. It enforces industry-standard patterns such as separating read and write operations, implementing proper transactional boundaries, and utilizing dedicated Command/Query objects for input and Result/ViewModel objects for output. This skill is ideal for developers building scalable Spring Boot applications who want to ensure consistent architecture, type safety, and clean code separation across their business logic and repository layers.

Características Principales

Automatically applies appropriate @Transactional and @Transactional(readOnly = true) annotations.
42 GitHub stars
Generates dedicated Data Transfer Objects (DTOs) and ViewModels for type-safe service interactions.
Implements Command Query Separation (CQS) by splitting services into distinct read and write classes.
Enforces clean package structures and naming conventions like XCmd, XQuery, and XResult.
Includes support for Component-based Mappers to translate domain entities to ViewModels efficiently.

Casos de Uso

Refactoring monolithic service classes into clean, maintainable Command and Query components.
Scaffolding a new microservice with a robust, scalable service layer architecture.
Standardizing transactional behavior and DTO patterns across a large Spring Boot development team.

Acerca de

Características Principales

Automatically applies appropriate @Transactional and @Transactional(readOnly = true) annotations.
42 GitHub stars
Generates dedicated Data Transfer Objects (DTOs) and ViewModels for type-safe service interactions.
Implements Command Query Separation (CQS) by splitting services into distinct read and write classes.
Enforces clean package structures and naming conventions like XCmd, XQuery, and XResult.
Includes support for Component-based Mappers to translate domain entities to ViewModels efficiently.

Casos de Uso

Refactoring monolithic service classes into clean, maintainable Command and Query components.
Scaffolding a new microservice with a robust, scalable service layer architecture.
Standardizing transactional behavior and DTO patterns across a large Spring Boot development team.