304-frameworks-spring-boot-security — Claude Code skill: guide
Configures Spring Boot security, endpoint authorization, and SecurityFilterChain. It helps implement JWT resource servers, method security, and safe headers.
npx skills add jabrena/plinth --skill 304-frameworks-spring-boot-security -a claude-codeWhat 304-frameworks-spring-boot-security does
This skill guides the setup of Spring Security across APIs and web endpoints. It structures SecurityFilterChain beans, handles OAuth2 or JWT resource server integration, and configures form login. The assistant reviews role scopes under least privilege, secures methods via @PreAuthorize, and stops sensitive data exposure in logs and error responses.
Strict verification gates govern every modification. The project must compile through ./mvnw compile or mvn compile before any edits start. If the build fails, the skill halts immediately. After applying changes, it runs ./mvnw clean verify to confirm project integrity.
What it helps with
- configure SecurityFilterChain and endpoint authorization rules
- integrate OAuth2 and JWT resource server patterns
- enforce method security using @PreAuthorize or @Secured
- apply safe security headers, CORS, and CSRF policies
- prevent credentials and sensitive data leaks in log files
Example prompts for the agent
- Review the Spring Boot SecurityFilterChain and add secure HTTP headers
- Configure a JWT resource server and restrict service methods with @PreAuthorize
- Harden CSRF and CORS settings for REST endpoints and prevent sensitive leaks in logs
How to install 304-frameworks-spring-boot-security
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 304-frameworks-spring-boot-security -a claude-code2Manually: put the files in place
~/.claude/skills/304-frameworks-spring-boot-security/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/304-frameworks-spring-boot-security/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 304-frameworks-spring-boot-security -a codex2Manually: put the files in place
.agents/skills/304-frameworks-spring-boot-security/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 304-frameworks-spring-boot-security -a cursor2Manually: put the files in place
.cursor/skills/304-frameworks-spring-boot-security/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth 304-frameworks-spring-boot-security2Manually: put the files in place
.github/skills/304-frameworks-spring-boot-security/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 304-frameworks-spring-boot-security -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/304-frameworks-spring-boot-securityManually: put the files in place
.devin/skills/304-frameworks-spring-boot-security/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 304-frameworks-spring-boot-security -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 304-frameworks-spring-boot-security
How to install 304-frameworks-spring-boot-security in Claude Code?
Run npx skills add jabrena/plinth --skill 304-frameworks-spring-boot-security -a claude-code in your terminal.
What does 304-frameworks-spring-boot-security do?
It provides guidelines and patterns to design, audit, and harden Spring Boot security layers, from JWT handling to method permissions.
What build requirements must be met before applying changes?
The project must compile without errors using mvn compile or ./mvnw compile. Execution stops immediately if this check fails.
Source text
SKILL.md · Apache-2.0
--- name: 304-frameworks-spring-boot-security description: Use when you need to design, review, or improve security in Spring Boot applications — including SecurityFilterChain, OAuth2/JWT resource server patterns, form login basics, method security (@PreAuthorize), CSRF and CORS for APIs, session fixation, security headers, exception handling, password encoding, and sensitive-data-safe logging. This should trigger for requests such as Add Spring Boot security support; Review Spring Boot security configuration; Improve API authorization in Spring Boot; Add JWT resource server security in Spring Boot; Harden Spring Boot security headers and CSRF settings. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # Spring Boot Security Guidelines Apply Spring Boot security best practices with secure-by-default API boundaries. **What is covered in this Skill?** - Spring Security configuration and SecurityFilterChain setup - Authentication and authorization policies for endpoints - Method-level security (@PreAuthorize / @Secured) - Principle of least privilege for roles and scopes - Secure error handling and denial responses - Sensitive data handling in logs and responses **Scope:** Apply recommendations based on the reference rules and good/bad examples. ## Constraints Before applying security changes, ensure the project compiles. After improvements, run full verification. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change - **SAFETY**: If compilation fails, stop immediately - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **BEFORE APPLYING**: Read the reference for detailed rules and examples ## When to use this skill - Add Spring Boot security support - Review Spring Boot security configuration - Improve API authorization in Spring Boot - Add JWT resource server security in Spring Boot - Harden Spring Boot security headers and CSRF settings - Implement method security with @PreAuthorize in Spring Boot ## Workflow 1. **Read reference and assess project context** Read `references/304-frameworks-spring-boot-security.md` and inspect the current project setup before proposing changes. 2. **Gather scope and decide target improvements** Identify requested outcomes, constraints, and the minimum safe set of changes to apply. 3. **Apply framework-aligned changes** Implement or refactor security-related configuration/code following the reference patterns and project conventions. 4. **Run verification and report results** Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions. ## Reference For detailed guidance, examples, and constraints, see [references/304-frameworks-spring-boot-security.md](references/304-frameworks-spring-boot-security.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth