review-resource

Resource architecture validation inspects your project structure against declared templates across schemas, repositories, services, controllers, and routes. It surfaces deviations from standardized naming, error handling, and event emission conventions to ensure consistent pattern usage.

Checking code for repository and service pattern deviations involves inspecting the module structure against established templates. This process identifies inconsistencies in file organization and standardized conventions, returning structured guidance for remediation.

Yes, you can enforce consistent naming conventions during refactoring by applying template validation to existing resources. It identifies structural deviations and provides remediation guidance to align existing modules with standardized architectural patterns.

The best way to surface architecture deviations during code review is to validate module implementations against declared resource templates. This enforces standardized error handling and file structure conventions, returning structured guidance for necessary remediation.

You need to validate resource implementation patterns when your codebase is undergoing feature creation or refactoring. This ensures consistent pattern usage across schemas, repositories, services, controllers, and routes, maintaining architectural consistency.