- Home
- Skills
- Shaul1991
- Shaul Agents Plugin
- Backend Java
backend-java_skill
- Makefile
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill shaul1991/shaul-agents-plugin --skill backend-java- SKILL.md719 B
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
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.