Loading...
Loading...
Found 2 Skills
Layering and boundaries, web vs public API, app layout (clients, routes, logging), ports/adapters, runtime-portable domain/shared/utils code, multi-tenancy, DDD layout, or anti-patterns.
Decide whether a technical dependency boundary is meaningful and design Ports, Adapters, dependency inversion, explicit injection, and test seams. Use for DI, interfaces, package direction, infrastructure isolation, and protocol translation; not for primarily business invariants or active failure diagnosis.