clean-architecture

To fix SOLID violations and broken layer boundaries in iOS, you must enforce inward-only dependency rules and isolate Presentation, Application, Domain, and Infrastructure layers. This Skill diagnoses these architecture issues and provides concrete remediation steps to restore domain framework independence.

Verifying dependency direction in TCA or MVVM refactors involves checking that domain layers remain framework-independent and presentation layers do not import infrastructure. This Skill flags cyclic dependencies and protocol injection issues, generating a severity-tagged improvement plan.

The best way to separate Presentation and Domain layers in Swift concurrency is to apply protocol-based injection for testability and ensure inward-only dependencies. This Skill analyzes your iOS feature and suggests specific refactor steps aligned to Swift concurrency patterns.

Yes, you can use Clean Architecture to improve testability and replaceability in existing iOS apps by enforcing layer separation and dependency inversion. This Skill evaluates whether your layers are properly isolated and wired, producing actionable before/after refactoring recommendations.

Your iOS domain layer depends on external frameworks due to broken dependency inversion rules where higher-level modules are coupled to lower-level infrastructure. This Skill identifies these SOLID violations and provides stepwise refactoring guidance to ensure domain framework independence.

Yes, this architecture review approach works with both TCA and Coordinator patterns by evaluating layer isolation and applying Clean Architecture guidance. It ensures boundaries remain testable and replaceable while applying iOS-appropriate patterns during refactors or PR reviews.