usecase-layer

You can validate your Usecase layer implementation by auditing API domain definitions, CRUD method patterns, and dependency injection. This Skill automatically reviews Usecase code to ensure correct business logic orchestration and adherence to Go Clean Architecture best practices.

The best way to handle DTO transformations in a Go Usecase layer is through inline DTO conversion. This approach enforces proper handling of optional fields and verifies Request/Response DTO validation rules to prevent common architectural flaws.

You can check error handling and transaction boundaries by auditing Usecase implementation patterns and repository interactions. This Skill verifies that your Go business logic correctly orchestrates transactions and handles errors before reaching production.

Yes, you can use this code review tool for existing Go Clean Architecture projects. It audits Usecase interfaces, validates API domain definitions, and verifies repository interaction patterns to catch potential architectural bugs in your current implementation.

Your Usecase layer architecture may fail to properly interact with repositories due to incorrect CRUD patterns or flawed dependency injection. This Skill guides proper repository interaction and transaction boundaries to prevent architectural failures.