Review Service Architecture

Review a functioning pre-production service before its structure becomes costly to change. Preserve confirmed business behavior. Ground the design in real entry flows, domain boundaries, and preservation constraints rather than a generic folder template.

This skill is read-only for the reviewed repository. Create review artifacts only under .agents/projects/<project>/; do not edit application code, root AGENTS.md, CI, configuration, documentation, schemas, or any other repository file. Implementation and adoption happen only in a separately approved workflow.

This is an enterprise architecture review, not a file-by-file style review and not a mandate to introduce layers. A layer earns its place only when it owns behavior, policy, or an infrastructure boundary that callers should not learn. Prefer domain packages with a clear downward dependency rule over global controllers, services, common, repositories, or types dumping grounds.