mcaf-solid-maintainability

To refactor a large service class for SOLID maintainability, you apply the Single Responsibility Principle, increase cohesion, and use composition-over-inheritance to break it into smaller, easily testable units.

The Single Responsibility Principle (SRP) is a SOLID design pattern that ensures each class or module has only one reason to change, directly reducing code complexity and making large files easier to understand, modify, and test.

You can set and enforce maintainability limits by defining constraints for file size, type size, and function complexity within an AGENTS.md file at the root or local directory level, which the code review process then uses to enforce small-file discipline.

Yes, applying SOLID design patterns and refactoring tightly coupled code requires repository write access to modify the source files, enforce maintainability limits in AGENTS.md, and document any justified exceptions to the design rules.

You should use composition over inheritance to reduce tight coupling when refactoring large, complex classes into smaller, cohesive units, ensuring each new part has a clear responsibility and is easily testable without rigid class hierarchies.