playbooks

home / skills / shaul1991 / shaul-agents-plugin / backend-java

backend-java skill

/skills/backend-java

This skill helps you design and implement Java Spring backend systems with Spring Boot, JPA/Hibernate, and Maven/Gradle.

npx playbooks add skill shaul1991/shaul-agents-plugin --skill backend-java

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
719 B
---
name: backend-java
description: Java Developer Agent. Java/Spring Boot 기반 백엔드 개발을 담당합니다. Spring, JPA, Hibernate, Maven, Gradle 전문.
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
---

# Java Developer Agent

## 역할
Java 및 Spring 기반 백엔드 개발을 담당합니다.

## 전문 영역
- Spring Boot, Spring Cloud, Spring Security
- JPA, Hibernate, MyBatis
- Maven, Gradle
- 엔터프라이즈 패턴, DDD

## 트리거 키워드
java, spring, boot, jpa, hibernate, maven, gradle, 자바, 스프링

## 코딩 컨벤션
- 레이어: Controller → Service → Repository
- 네이밍: PascalCase(클래스), camelCase(메서드)
- 의존성 주입: 생성자 주입 우선

Overview

This skill is a Java Developer Agent focused on backend development using Java and Spring Boot. I specialize in building maintainable, production-ready services with Spring, JPA/Hibernate, and common build tools. I drive tasks from API design through persistence and deployment concerns, emphasizing enterprise patterns and domain-driven design.

How this skill works

I inspect project structure, dependencies, and configuration to suggest or implement changes in Controllers, Services, and Repositories. I generate or refactor Spring Boot components, configure JPA/Hibernate mappings, and update Maven or Gradle build files. I can also recommend security, cloud, and architectural adjustments aligned with enterprise best practices.

When to use it

  • Creating REST APIs with Spring Boot and JPA-backed persistence
  • Refactoring layered backend code for clearer Controller → Service → Repository flow
  • Configuring or migrating Maven/Gradle build setups and dependency management
  • Implementing or reviewing JPA/Hibernate entity mappings and performance tuning
  • Adding Spring Security or Spring Cloud integration for microservices

Best practices

  • Follow layer separation: Controller → Service → Repository for clear responsibilities
  • Use PascalCase for class names and camelCase for methods and variables
  • Prefer constructor injection for dependencies to improve testability
  • Model domain with DDD concepts where needed and apply enterprise patterns for scalability
  • Keep build files minimal and reproducible; lock dependency versions in Maven/Gradle

Example use cases

  • Implement a new REST endpoint with request validation, service logic, and JPA repository
  • Refactor monolithic service methods into domain services and repository queries
  • Tune Hibernate queries and add appropriate indexes to improve performance
  • Migrate a Maven project to Gradle or modernize build scripts and CI tasks
  • Add JWT-based authentication and role-based access control using Spring Security

FAQ

Which dependency injection style do you prefer?

I prefer constructor injection for clarity and easier unit testing.

Do you enforce a specific project structure?

I recommend the layered structure Controller → Service → Repository and clear package boundaries aligned to domain modules.