Keep backend boundaries clear and domain rules intact.
backend architecture
Designs or reviews backend domain models and dependency boundaries using architecture patterns suited to the concrete problem.
When to use it
Use for aggregate modeling, bounded contexts, use-case isolation, or architecture refactoring, but not routine CRUD changes.
Give it a backend domain or dependency problem in a project; it delivers the requested model, patch, or review with boundary tradeoffs.
What you provide
No additional actions listed in the analysis.
No setup requirements listed in the analysis.