clean-architecture-checker

What problem does it solve?

This Skill ensures that all code in the Polibase project strictly adheres to Clean Architecture principles, preventing architectural decay and promoting maintainability. It automates the verification of dependency rules, entity independence, repository patterns, DTO usage, and type safety, significantly reducing code review time and ensuring long-term project health.

Core Features & Use Cases

• Dependency Rule Enforcement: Verifies that dependencies always point inward (Domain ← Application ← Infrastructure ← Interfaces), maintaining strict layer separation.
• Entity Independence Check: Ensures domain entities remain free from external framework dependencies (e.g., SQLAlchemy, Streamlit), preserving core business logic purity.
• Repository & DTO Pattern Validation: Confirms proper implementation of asynchronous repository patterns and consistent use of DTOs for data transfer between layers.
• Use Case: When you're developing a new feature or reviewing a pull request, this skill automatically checks if the code follows all Clean Architecture guidelines, such as correct layer imports and DTO usage, ensuring the codebase remains clean, testable, and scalable.

Quick Start

I am reviewing a new feature that modifies files across src/domain/ and src/application/. Check if it complies with Clean Architecture dependency rules and DTO usage.