clean-architecture-review

Clean Architecture validation analyzes your iOS codebase to ensure Presentation, Domain, and Data layers are properly separated with correct dependency flow. It checks MVVM, UseCase, Repository, and dependency injection patterns, then reports compliance scores, violations, and refactoring steps to prevent tangled layers and maintenance issues.

Yes. This validates MVVM implementation by confirming ViewModels don't contain UI logic or direct API calls, ensures UseCase pattern uses protocol + implementation separation, verifies Repository pattern boundaries, and checks constructor-based dependency injection via Swinject throughout your codebase.

It identifies violations like ViewModels calling APIs directly, business logic in the Presentation layer, Domain layer depending on UI frameworks, missing Repository pattern in Data layer, and incorrect dependency direction. Each violation is flagged with actionable refactoring guidance.

Run architecture review on your module to get an instant compliance report classifying files into Presentation, Domain, and Data layers, flagging any boundary crossings, and scoring adherence. Use it during refactoring checkpoints to catch issues before they compound.

Yes. It specifically enforces constructor-based dependency injection patterns using Swinject, verifying that dependencies are properly resolved and injected rather than created inline, ensuring loose coupling and testability across your architecture.

Activate architecture review early during feature development and refactoring cycles. Regular validation catches layer violations, pattern mismatches, and dependency flow issues incrementally, reducing the cost of fixing structural problems later.