repository-placement

Repository interfaces belong in the use-case layer to preserve domain purity by preventing domain models from importing persistence concerns. Placing them in the domain layer couples your core business logic to infrastructure dependencies, violating the intended dependency direction of Clean Architecture.

To enforce clean architectural boundaries, move repository interface declarations into the use-case layer and adjust imports so domain models no longer reference repository contracts. This separation ensures domain logic remains independent of persistence responsibilities and infrastructure adapters.

You need a project structure with separate domain/, usecases/, and interface-adapters/ directories. This layout allows repository interfaces to reside in the use-case layer while implementation details stay in interface adapters, ensuring domain models remain pure and free of persistence imports.

If your domain layer imports repository interfaces, your domain models become coupled to persistence concerns, breaking domain purity. This violates Clean Architecture's dependency direction, making the core business logic harder to test and maintain independently of infrastructure changes.

You can check for incorrect imports by scanning your domain layer for references to repository contracts or interfaces. The Skill verifies that repositories are not imported into domain models and confirms interfaces are declared in the use-case layer to maintain proper architectural boundaries.

Yes, existing Clean Architecture projects can relocate repository interfaces from the domain layer to the use-case layer. Adjust imports across domain models and interface adapters to enforce the correct dependency direction and restore domain purity without rewriting core business logic.