clean-architecture-guide

Clean architecture structures a PhotoGallery project by separating domain, infrastructure, and presentation layers with explicit dependency rules. This blueprint enforces dependency inversion and applies repository, specification, and domain event patterns for scalable, framework-agnostic design.

The dependency rule in layered architecture mandates that inner layers like domain logic must not depend on outer layers like infrastructure or presentation. This Skill defines explicit dependency rules where dependencies always point inward toward the domain core.

Yes, you can use domain-driven design patterns for a PhotoGallery application. This blueprint provides tailored coverage of the Repository, Specification, Domain Events, and Dependency Injection patterns to organize domain logic and data access across feature boundaries.

Organizing domain, infrastructure, and presentation layers requires explicit dependency rules and pattern coverage like dependency injection. This blueprint delivers a scalable project layout suitable for Phase 2+ by aligning architecture decisions with use case organizational strategies.

Choose layered architecture over vertical slice when strict separation between domain, infrastructure, and presentation is required. This blueprint provides use case examples and organizational strategies comparing both approaches to align with your scalable project requirements.