Separation of Concerns Architect
Enforces clean architecture patterns through structured folders and strict dependency rules for maintainable, scalable software development.
This skill guides Claude in implementing a robust Separation of Concerns (SoC) architecture, organizing code into features (verticals), platform (horizontals), and shell layers. It ensures clear boundaries between external clients, domain logic, and orchestration, preventing spaghetti code by enforcing a strict 'Vertical/Horizontal' mental model. By applying specific principles like separating intent from execution and isolating state dependencies, it helps developers build systems that are easier to test, refactor, and evolve over time.
Características Principales
01Enforces 'Vertical Slice' organization via feature-specific entrypoints and use-cases.
02Centralizes shared capabilities within a structured platform/ domain and infra layer.
03Refactors code based on state dependency and semantic naming alignment.
04121 GitHub stars
05Separates intent from execution to ensure high-level business flow readability.
06Validates strict dependency rules, such as preventing entrypoints from touching domain logic.
Casos de Uso
01Refactoring monolithic service files into a clean, feature-based directory structure.
02Scaffolding new project modules with pre-defined architectural boundaries and layers.
03Automating code reviews to identify leaked domain logic or improper cross-feature dependencies.