What problem does it solve? Repository interfaces often drift into anti-patterns: names derived from tables or DTOs, methods leaking domain logic or SQL terminology, and return types exposing infrastructure records instead of aggregates. This Skill detects those violations during code review, new implementation, or refactoring and proposes concrete fixes. ## Core Features & Use Cases - Naming Rule Enforcement: Verifies repository names follow the AggregateName + Repository convention and flags infrastructure terms like Table, Dto, Entity, Record, or Row. - CQS Method Validation: Checks that each method is either a query returning aggregates with no side effects or a command accepting aggregates and returning void, covering single-item, multi-item, synchronous, and asynchronous (Future, async/await, Result/Either) patterns. - Anti-Pattern Detection: Identifies DTO/record return types, domain-logic method names (leave, activate, cancel), SQL-style names (insert, update, select, upsert), and repositories calling other repositories instead of coordinating in the use-case layer. - Use Case: During a pull request review, ask the AI to check a new OrderRepository interface; it flags that findById returns OrderDto and that store returns an OrderId, then suggests corrected signatures. ## Quick Start Ask the AI to review the design of your repository interface, for example by saying "Review this OrderRepository interface for DDD design violations."
