Verified:GitHub

clean-architecture-placement

Place new and refactored code into Clean Architecture layers with correct namespaces.

Updated Apr 9, 2026

Search Tags:#refactoring #domain-driven-design #clean-architecture #software-design #project-organization #layered-architecture #architecture-guidelines

Ready to run

npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill clean-architecture-placement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clean-architecture-placement
Source: https://github.com/SergeuMatyasov/dotnet-shared-skills/tree/main/clean-architecture-placement
Command: npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill clean-architecture-placement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Этот навык поможет поддерживать четкую архитектуру проекта, обеспечивая размещение кода в правильном слое и предотвращая смешение бизнес-логики с инфраструктурой при создании или переносе файлов.

Core Features & Use Cases

Определяет целевые слои (Domain, Application, Infrastructure, EFCore, Host, Shared, modules, tests) и руководит их заполнением по функциональности.
Помогает организовать новый функционал и реорганизацию существующего кода согласно принципам чистой архитектуры.
Подсказывает, как распределять ответственность между слоями и как переиспользовать общие элементы без нарушения зависимостей.

Quick Start

Помести новый код или перенеси существующий в соответствующий слой (Domain, Application, Infrastructure, EFCore, Host, Shared) согласно чистой архитектуре.

Frequently Asked Questions about clean-architecture-placement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce clean architecture boundaries when organizing a software project?▼

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.

What is the best way to refactor existing code into a layered architecture?▼

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.

How do I separate domain logic from infrastructure when adding new features?▼

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.

Can I use this approach to organize modules and tests in a domain-driven design project?▼

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.

When do I need to validate folder placement and namespace updates during refactoring?▼

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.