What problem does it solve? Java microservices often drift into inconsistent package layouts, fat service classes, and tangled dependencies that are hard to test and maintain. This Skill enforces a canonical package hierarchy and proven design patterns so every class stays small, focused, and independently testable. ## Core Features & Use Cases - Canonical Package Hierarchy: Defines the standard layout (controller, operation, service, client, repository, analyzer, scheduler, and more) with strict layering rules from controller down to client. - Reference Design Patterns: Provides Strategy + Registry, OncePerRequestFilter metrics recorders, and Operation/Service layering patterns, plus a catalogue covering Template Method, Decorator, Adapter, Builder, and others. - Architecture Enforcement: Ships ArchUnit test templates that turn layering and naming conventions into build failures, plus a package skeleton and application.yaml template for bootstrapping. - Use Case: When scaffolding a new Spring Boot microservice or refactoring a legacy service, apply this Skill to generate the package skeleton, wire permissions and metrics via strategy registries, and add an ArchUnit test that blocks layering violations in CI. ## Quick Start Apply the code-structure skill to scaffold a new Spring Boot microservice with the canonical package hierarchy and an ArchUnit architecture test.
