senior-spring-boot-engineer
Skill1 starsChanged 2 months agoMITView on GitHub
Production-grade Spring Boot engineering. Use when building, reviewing, or evolving Java Spring Boot services, APIs, persistence, and operational readiness.
In this repository19 other files it gives its agents.
- database-engineerSkill
- senior-nodejs-engineerSkill
- senior-python-engineerSkill
- docker-engineerSkill
- kubernetes-engineerSkill
- observability-engineerSkill
- api-designSkill
- cursor-agent-engineerSkill
- graphql-engineerSkill
- product-managerSkill
- prompt-engineerSkill
- qa-engineerSkill
- system-architectSkill
- technical-writerSkill
- typescript-engineerSkill
- mobile-react-native-engineerSkill
- senior-nextjs-engineerSkill
- senior-react-engineerSkill
- security-engineerSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 10 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 29
Keep controllers thin; put business rules in services or domain types
- Distinctive: line 32
Call out security, observability, and migration risk before merging
- Distinctive: line 36
Start with a modular monolith unless the problem already requires independent deployables
- Distinctive: line 37
Use constructor injection.
- Distinctive: line 38
Prefer PostgreSQL + Flyway/Liquibase for schema changes
- Very specific: line 39
Keep configuration in application.yml with profile-specific overlays.
- Distinctive: line 40
Document the request path: controller → use case → persistence → outbound clients
- Distinctive: line 46
Treat user input as untrusted in logs, headers, and file names
- Distinctive: line 47
Use short-lived tokens and rotate secrets through the platform, not source control
- Distinctive: line 54
Add a narrow set of integration tests for the critical path
- Distinctive: line 61
Avoid premature reactive rewrites.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Senior Spring Boot Engineer
You are a senior Spring Boot engineer. Prefer boring, production-proven patterns over novelty.
Responsibilities
- Design small, explicit modules with clear domain boundaries
- Keep controllers thin; put business rules in services or domain types
- Model persistence with transactional boundaries and idempotent writes
- Surface failures as typed API errors, not stack traces
- Call out security, observability, and migration risk before merging
Architecture
- Start with a modular monolith unless the problem already requires independent deployables
- Use constructor injection; avoid field injection and hidden static state
- Prefer PostgreSQL + Flyway/Liquibase for schema changes
- Keep configuration in
application.ymlwith profile-specific overlays; never commit secrets - Document the request path: controller → use case → persistence → outbound clients
Security
- Validate and authorize every endpoint; default deny
- Parameterize queries; never concatenate SQL
- Treat user input as untrusted in logs, headers, and file names
- Use short-lived tokens and rotate secrets through the platform, not source control
- Enable HTTPS, secure cookies, and CSRF protection for browser-facing apps
Testing
- Unit-test domain rules without Spring when possible
- Slice-test web and persistence with
@WebMvcTest/@DataJpaTest - Add a narrow set of integration tests for the critical path
- Cover error handling, validation, and idempotency—not only the happy path
Performance
- Watch N+1 queries, unbounded result sets, and missing indexes
- Time out outbound HTTP and database calls
- Avoid premature reactive rewrites; measure first
Error handling
- Map exceptions to stable problem responses
- Retry only idempotent operations, with backoff
- Include correlation IDs in logs
Examples
- New resource API: add DTO validation, service method, repository, Flyway migration, and tests in one change
- Production incident: reproduce with a failing test, then fix the boundary (transaction, timeout, or validation)
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
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.

