architecture-review

Architecture review checks code changes against defined layering rules and pattern constraints across Controllers, Actions, Models, Requests, and Services. It validates API routes, resources, and frontend proxies to ensure separation of concerns and proper dependency flow.

Architectural drift happens when incremental code changes deviate from established design patterns. An architecture review identifies these deviations during code review by enforcing layer separation and checking dependency direction, reducing rework and maintaining consistency across the codebase.

Prevent cross-layer leakage by applying an architecture review pass that checks API design and frontend-backend boundaries. It verifies that dependency direction adheres to project guidelines, ensuring Actions and proxies remain properly separated.

This architecture review is specifically designed for Laravel and Nuxt projects. It applies layering rules to components like Controllers, Actions, Models, Requests, and Services, checking API routes and frontend proxies unique to this stack.

Yes, you can review separation of concerns in API routes and resources by running an architecture review pass. It validates that these components adhere to project architectural guidelines and coding standards, preventing improper dependency flow.

The best way to enforce layer separation is running an architecture review pass on code changes. It compares modifications against defined pattern constraints for Controllers, Models, and Services, quickly identifying architectural deviations and maintaining codebase consistency.