About 504-frameworks-micronaut-security
A skill for Micronaut developers configuring and reviewing application security. It covers authentication, role-based authorization, route protection, least privilege, and secure handling of errors and sensitive data.
Key features
- 01认证配置指导
- 02基于角色的授权策略
- 03端点与路由保护
- 04最小权限边界设计
- 05安全处理错误与敏感数据
Use cases
- 01为 Micronaut API 配置安全机制
- 02审查 JWT 与认证设置
- 03强化控制器的路由授权规则
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ jabrena/ plinth --skill 504-frameworks-micronaut-securityAfter installing, type/504-frameworks-micronaut-securityin Claude Code to confirm it loaded.
Bundled filesreferences/504-frameworks-micronaut-security.md
Details
From the project READMEMicronaut Security Guidelines
Apply Micronaut security best practices with secure-by-default API boundaries.
What is covered in this Skill?
- Micronaut security configuration and authentication setup
- Authorization with @Secured and role-based policies
- Endpoint and route protection strategy
- Least-privilege design and policy boundaries
- Secure error/denial behavior
- 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 compileormvn compilebefore applying any change - SAFETY: If compilation fails, stop immediately
- VERIFY: Run
./mvnw clean verifyormvn clean verifyafter applying improvements - BEFORE APPLYING: Read the reference for detailed rules and examples
When to use this skill
- Add Micronaut security support
- Review Micronaut security configuration
- Improve API authorization in Micronaut
- Add JWT security in Micronaut
- Harden Micronaut route authorization rules
- Implement @Secured policies in Micronaut controllers
Workflow
- Read reference and assess project context
Read references/504-frameworks-micronaut-security.md and inspect the current project setup before proposing changes.
- Gather scope and decide target improvements
Identify requested outcomes, constraints, and the minimum safe set of changes to apply.
- Apply framework-aligned changes
Implement or refactor security-related configuration/code following the reference patterns and project conventions.
- 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/504-frameworks-micronaut-security.md.