What problem does it solve? Adding per-resource authorization to a Spring Boot microservice often leads to tangled if/else logic scattered across controllers and handlers. This Skill scaffolds a clean, pluggable authorization layer that dispatches permission checks by caller type, so new caller contexts can be added without modifying existing code. ## Core Features & Use Cases - Pluggable Strategy + Handler + Registry architecture: Generates a PermissionsHandler, PermissionsRegistry, CallerContextResolver, and per-context PermissionsCheckStrategy components wired via Spring list injection. - Vendor-neutral plug-points: Ships defaults for Spring Security's SecurityContextHolder and an abstract ResourceAuthorizationSource, letting teams plug in their own token shapes and authorization back-ends. - Complete test and validation guidance: Includes required unit test cases, component test wiring with a mock handler, and an end-to-end validation matrix covering 401/403/2xx scenarios. - Use Case: When creating a new microservice that exposes user-facing data, invoke this Skill to generate the full permission package, configure allowed OAuth2 scopes for service accounts, and enforce per-resource checks inside every operation. ## Quick Start Ask the AI to apply the permissions skill to scaffold an authorization layer for your Spring Boot service, specifying your base package, accepted caller contexts, and resource identifier.
