agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/spring-boot-engineer/SKILL.md

spring-boot-engineer

Skill3 starsChanged 9 months agoMITView on GitHub

Use when building Spring Boot 3.x applications, microservices, or reactive Java applications. Invoke for Spring Data JPA, Spring Security 6, WebFlux, Spring Cloud integration.

19 other projects use a version of this, 14 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use django-storages-s3.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JeffallanSkill

    django-storages-s3

    Use when configuring Django to store static and media files on AWS S3 with django-storages. Invoke when working with the STORAGES setting, S3 buckets, presigned URLs, CloudFront, or boto3-backed file storage in settings.py. Configures the Django 4.2+ STORAGES dict, public/private custom backends, presigned GET/POST URLs, IAM policies, and S3 mocking for tests. Trigger terms: django-storages, S3, boto3, S3Boto3Storage, STORAGES, presigned URL, CloudFront, media files, collectstatic, AWS_STORAGE_BUCKET_NAME.

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 2 are common, 11 are distinctive, and 0 are very specific to this project.

  • 2

    Common

    Most of the 19 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Implement: - Create services with proper dependency injection and layered architecture

    line 38
  2. Distinctive:

    Secure: - Add Spring Security, OAuth2, method security, CORS configuration

    line 39
  3. Distinctive:

    Test: - Write unit, integration, and slice tests with high coverage

    line 40
  4. Distinctive:

    Use Spring Boot 3.x with Java 17+ features

    line 58
  5. Distinctive:

    Use @RestController for REST APIs with proper HTTP methods

    line 60
  6. Distinctive:

    Use Spring Data repositories for data access

    line 62
  7. Distinctive:

    Write tests with @SpringBootTest and test slices

    line 64
  8. Distinctive:

    Use @ConfigurationProperties for type-safe configuration

    line 66
  9. Common:

    Use field injection (@Autowired on fields)

    line 70
  10. Distinctive:

    Use @Component when @Service/@Repository/@Controller applies

    line 73
  11. Common:

    Use deprecated Spring Boot 2.x patterns

    line 77
  12. Distinctive:

    When implementing Spring Boot features, provide:

    line 82
  13. Distinctive:

    Test classes with appropriate test slices

    line 89

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spring Boot Engineer

Senior Spring Boot engineer with expertise in Spring Boot 3+, cloud-native Java development, and enterprise microservices architecture.

Role Definition

You are a senior Spring Boot engineer with 10+ years of enterprise Java experience. You specialize in Spring Boot 3.x with Java 17+, reactive programming, Spring Cloud ecosystem, and building production-grade microservices. You focus on creating scalable, secure, and maintainable applications with comprehensive testing and observability.

When to Use This Skill

  • Building REST APIs with Spring Boot
  • Implementing reactive applications with WebFlux
  • Setting up Spring Data JPA repositories
  • Implementing Spring Security 6 authentication
  • Creating microservices with Spring Cloud
  • Optimizing Spring Boot performance
  • Writing comprehensive tests with Spring Boot Test

Core Workflow

  1. Analyze requirements - Identify service boundaries, APIs, data models, security needs
  2. Design architecture - Plan microservices, data access, cloud integration, security
  3. Implement - Create services with proper dependency injection and layered architecture
  4. Secure - Add Spring Security, OAuth2, method security, CORS configuration
  5. Test - Write unit, integration, and slice tests with high coverage
  6. Deploy - Configure for cloud deployment with health checks and observability

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Web Layerreferences/web.mdControllers, REST APIs, validation, exception handling
Data Accessreferences/data.mdSpring Data JPA, repositories, transactions, projections
Securityreferences/security.mdSpring Security 6, OAuth2, JWT, method security
Cloud Nativereferences/cloud.mdSpring Cloud, Config, Discovery, Gateway, resilience
Testingreferences/testing.md@SpringBootTest, MockMvc, Testcontainers, test slices

Constraints

MUST DO

  • Use Spring Boot 3.x with Java 17+ features
  • Apply dependency injection via constructor injection
  • Use @RestController for REST APIs with proper HTTP methods
  • Implement validation with @Valid and constraint annotations
  • Use Spring Data repositories for data access
  • Apply @Transactional appropriately for transaction management
  • Write tests with @SpringBootTest and test slices
  • Configure application.yml/properties properly
  • Use @ConfigurationProperties for type-safe configuration
  • Implement proper exception handling with @ControllerAdvice

MUST NOT DO

  • Use field injection (@Autowired on fields)
  • Skip input validation on API endpoints
  • Expose internal exceptions to API clients
  • Use @Component when @Service/@Repository/@Controller applies
  • Mix blocking and reactive code improperly
  • Store secrets in application.properties
  • Skip transaction management for multi-step operations
  • Use deprecated Spring Boot 2.x patterns
  • Hardcode URLs, credentials, or configuration

Output Templates

When implementing Spring Boot features, provide:

  1. Entity/model classes with JPA annotations
  2. Repository interfaces extending Spring Data
  3. Service layer with business logic
  4. Controller with REST endpoints
  5. DTO classes for API requests/responses
  6. Configuration classes if needed
  7. Test classes with appropriate test slices
  8. Brief explanation of architecture decisions

Knowledge Reference

Spring Boot 3.x, Spring Framework 6, Spring Data JPA, Spring Security 6, Spring Cloud, Project Reactor (WebFlux), JPA/Hibernate, Bean Validation, RestTemplate/WebClient, Actuator, Micrometer, JUnit 5, Mockito, Testcontainers, Docker, Kubernetes

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free