spring-boot-skills
A set of Claude Code and Codex skills that teach the agent to write Spring Boot by your conventions and templates
- 357 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The skills consist of instructions, examples and code templates
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/spring-boot-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skills consist of instructions, examples and code templates
This is third-party code. Review the repository files before installing.
What it does
Each skill is a Markdown file the agent reads before touching Spring Boot code, so it follows the right practices instead of generic web examples. Topics span architecture, REST conventions, data and JPA, Flyway migrations, security, messaging, observability, container deployment and more. Skills ship with good and bad code examples and ready class templates. The catalog is split into two trees for Spring Boot 3 and Spring Boot 4. It installs as a marketplace plugin or by copying the needed folders into the skills directory.
Who it is for. For Java developers on Spring Boot who want the agent to write code in their project's style.
Good fit when
- The agent generates Spring Boot with foreign conventions and stale practices
- You need shared rules for controllers, DTOs, error handling and API versioning
- You are moving between Spring Boot 3 and 4 and want current practices
Not a fit when
- The project is not on Spring Boot
- You need an executable tool rather than reference instructions for the agent
Example request
Add an orders endpoint following the skill's REST conventions, with our response wrapper and versioningLimitations
These are reference instructions and templates, not an executable tool, and the agent writes the code itself. The practices are tied to Spring Boot 3 and 4, so check the official sources before upgrading. The skills are in English.
How to disable. Uninstall the spring-boot-skills plugin via claude plugin or remove the copied folders from the .claude/skills directory.
FAQ
How do the Boot 3 and Boot 4 trees differ?
Practices and examples are tuned to the matching Spring versions, and shared topics appear in both trees.
Can I skip the plugin?
Yes, you copy the needed skill folders straight into the project's .claude/skills.
Discussion
No questions or reviews yet.
Related
SkillsSixteen Spring Boot skills: the agent explores the application first, then edits JPA, DTOs, REST, Security, Kafka and tests.
A set of 14 skills for Java Spring Boot, from requirements analysis and code generation to tests, review and Docker deployment.
Skills for Java projects: code review, Spring Boot, JPA, concurrency, Java version migration, Maven audits and security
Six skills for Java work: Spring Boot 4, Modulith checks, jSpecify, code review and the Progen project generator.
A plugin with 8 skills and 6 agents for Claude Code: Spring Boot 4, Java 21, JPA, tests and Kubernetes by one rule set.
A skill that creates Spring Boot apps: takes the latest version from start.spring.io and adds Docker, Vue or React, PostgreSQL.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| spring-boot-skills (this card) | no | 357 | |
| AIGuide Skills | no | 742 | two AIGuide skills |
| BootUI | no | 334 | a skill and MCP server that let an agent inspect requests |
README in short
The README explains that agents often invent Spring Boot code: field injection instead of constructor injection, a new error hierarchy, hand-written schema instead of Flyway. The skills give the agent the project's conventions before it edits code. The catalog holds thirty-plus topics in two version trees for Boot 3 and Boot 4, each with examples and templates. Install goes through the Claude Code and Codex plugin marketplace or by copying folders into the skills directory. Repeatable commands such as endpoint generation and test writing are on the roadmap.
README badge
Original SKILL.md
--- name: rest-api-conventions description: > Use when generating REST controllers, DTOs, success response contracts, pagination, HTTP status mapping, or API versioning. For RFC 9457 exception and error response formatting, use problem-details-rfc9457 unless the project explicitly requires a legacy error envelope. --- # REST API Conventions ## Project Contract Inspect existing controllers, tests and OpenAPI before choosing a response contract. Preserve the project's IDs, response shape and versioning strategy. Do not migrate unrelated endpoints while adding one route. The envelope below is an optional convention for a project that uses it; plain success DTOs are equally valid. A 204 response has no body. Success and error formats are independent: an existing success envelope can coexist with RFC 9457 errors. Use one consistent error policy; choose the legacy error examples below only when the project already requires that format.