What problem does it solve? Code that passes a blocking P1/P2 review gate can still accumulate design debt: bloated methods, duplicated logic, premature abstractions, N+1 queries, and controllers bypassing service layers. This Skill provides a consistent checklist of design principles and anti-patterns so reviewers catch structural quality issues that a correctness-focused gate misses. ## Core Features & Use Cases - Design principle checks: Nine concrete rules covering Single Responsibility, DRY, YAGNI, KISS, Dependency Inversion, DDD entity/validator separation, service-layer enforcement, N+1 query detection, and streaming of large payloads. - Anti-pattern catalog: Named smells to flag, such as 30+ line multi-responsibility methods, magic numbers, speculative abstractions with one implementation, and lazy-load loops in JPA. - Non-blocking report format: A Markdown output template for reporting quality findings separately from the blocking P1/P2 review verdict. - Use Case: During a pull request review of a Spring service, use this Skill to spot that OrderService validates, persists, and formats in one method and that findAllById plus per-item lazy loading triggers N+1 queries, then report both as non-blocking quality notes. ## Quick Start Review the attached diff against the code quality principles and report any SOLID, DRY, or N+1 violations as non-blocking notes.
