clean-architecture-placement

To enforce clean architecture boundaries, organize your software project into distinct Domain, Application, Infrastructure, EFCore, Host, Shared, and test layers. This prevents mixing business logic with infrastructure and ensures correct layer placement across features.

Refactoring into a layered architecture involves moving existing code into appropriate Domain, Application, or Infrastructure layers during folder restructuring. The skill validates placement decisions against team conventions and updates namespaces to maintain correct dependencies.

Separate domain logic from infrastructure by placing new functionality into the correct clean architecture layer during file creation. This ensures business rules remain isolated within the Domain layer while external concerns stay in Infrastructure.

Yes, you can organize modules and tests in a domain-driven design project by applying this structure. It defines target layers including Domain, Application, Shared, and tests, guiding their population by feature ownership and responsibility distribution.

You need to validate folder placement and update namespaces whenever you create new files, refactor existing code, or restructure folders. This ensures alignment with defined folder structures and prevents dependency violations across clean architecture layers.