001-commands-inventory
Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing…
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
$ npx -y skills add jabrena/plinth --skill 304-frameworks-spring-boot-security --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/304-frameworks-spring-boot-securityContext preview
The summary Claude sees to decide when to auto-load this skill.
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
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.18.0
Apply Spring Boot security best practices with secure-by-default API boundaries.
**What is covered in this Skill?**
**Scope:** Apply recommendations based on the reference rules and good/bad examples.
Before applying security changes, ensure the project compiles. After improvements, run full verification.
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.
For detailed guidance, examples, and constraints, see [references/304-frameworks-spring-boot-security.md](references/304-frameworks-spring-boot-security.md).
Languages: Español · 中文 Help this project grow: Become a sponsor
Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing…
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing…
Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing…
Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands),…
Use when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or .codex/agents, selecting the destination…
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user…