How to use the Spring Boot Patterns agent skill

What the skill makes the agent do

When the skill is installed, the agent follows a set of Spring Boot patterns when you ask for backend work. The skill covers how to structure controller, service and repository layers, validate requests with DTOs, handle errors consistently, paginate and sort results, cache data, run async tasks, log requests and rate-limit traffic with Bucket4j.

The skill is a single file, SKILL.md. It is a reference of code examples and guidance, written in Spanish, and it does not include scripts.

How to install the springboot-patterns skill

Download the ZIP of the skill from this page. Then install it in one of two ways.

For a personal install, unzip the file into ~/.claude/skills/. For a single project, unzip it into the project's .claude/skills/ folder. You can also upload the skill in the Claude apps under Settings → Capabilities → Skills.

• Personal install: unzip into ~/.claude/skills/
• Project install: unzip into your project's .claude/skills/ folder
• Claude apps: upload under Settings → Capabilities → Skills

How to trigger the skill with natural requests

You do not need a special command. Describe backend work in a Spring Boot project and the agent can use the skill when the request matches its description: building REST APIs with Spring MVC or WebFlux, structuring controller → service → repository layers, configuring Spring Data JPA, caching or async processing, and adding validation, exception handling or pagination.

Be specific about the Spring Boot part of the task. A request such as 'add a paginated list endpoint for markets using Spring MVC' gives the agent a clear match for the skill.

• Build a REST controller with paginated GET and validated POST endpoints for orders in Spring Boot
• Add a global exception handler that returns a consistent error body for validation failures
• Cache product lookups by id in my Spring Boot service and show the required configuration
• Add a rate limit of requests per client IP to my Spring Boot API using Bucket4j

What the examples cover

The source file includes Java examples for each pattern. Use them as a starting point and adapt names, packages and types to your project.

The REST example uses a controller with @RequestMapping, @Validated, and paginated list and create methods. The validation example uses a Java record with @NotBlank, @Size and @NotEmpty constraints. The exception example uses @ControllerAdvice to turn validation and access-denied errors into API error responses. The caching example needs @EnableCaching in a configuration class, and the async example needs @EnableAsync. The logging example uses SLF4J, and a filter example logs method, URI, status and duration for each request.

• REST controllers and repository methods
• Validation with DTO records
• Global error handling with @ControllerAdvice
• Caching with @Cacheable and @CacheEvict
• Async tasks with @Async and CompletableFuture
• Structured logging with SLF4J
• Pagination and sorting with PageRequest
• Retry helper for external calls with exponential backoff
• Rate limiting filter with Bucket4j

What you need before using the skill

The skill is for Java backend work. Your project needs Java and a Spring Boot project that uses Spring MVC or WebFlux. The repository examples assume Spring Data JPA. The rate-limiting example needs Bucket4j. Kafka is only needed if you use the event-driven pattern.

The skill itself does not install these libraries for you. Check that your project already has the dependencies the code you ask for will use.

• Java and a Spring Boot project (Spring MVC or WebFlux)
• Spring Data JPA for repository examples
• Bucket4j for the rate-limiting example
• Kafka only if you use the event-driven pattern

Safety notes: scripts, network and rate limiting

The skill does not run scripts and does not use the network. It only gives the agent guidance and code examples to read.

The rate-limiting section needs care. The file warns that X-Forwarded-For is not trustworthy by default because clients can spoof it. Forwarded headers should only be used when the app sits behind a trusted reverse proxy, ForwardedHeaderFilter is registered as a bean, server.forward-headers-strategy is set to NATIVE or FRAMEWORK, and the proxy overwrites rather than appends X-Forwarded-For. Without that setup, the file says to use request.getRemoteAddr() directly. Review any rate-limiting code before you rely on it in production.

• No scripts are included in the skill
• The skill does not use the network
• Do not trust X-Forwarded-For unless the proxy setup described in the file is in place
• Review rate-limiting code before using it in production

Tips for getting good results

Name your framework stack in the request, including Spring MVC or WebFlux, and whether you use Spring Data JPA. The file is written around these choices, so the agent's output will match your project more closely.

Ask for one pattern at a time, such as caching or error handling, and check the output against your existing code. The examples are reference code, so they may need changes for your domain types, exception classes and configuration.

• State whether you use Spring MVC or WebFlux
• Mention Spring Data JPA if you need repositories
• Ask for one pattern at a time and review the result
• Expect to adapt names and types to your own code