architecture-boundary-enforcer

Enforcing architectural boundaries involves validating type ownership and dependency direction across domain, app, HTTP, and infra layers to prevent code tangling. This Skill reviews placement and dependency flows to maintain separation of concerns.

Preventing DTO leakage requires enforcing distinct structures for network transport versus internal domain representation. This Skill validates Data Transfer Object and model separation to ensure request DTOs do not expose internal infrastructure details.

Authentication and session management logic should be placed within the application layer. This Skill reviews the secure handling of credentials, hashing, and session data to ensure auth flows are correctly implemented across architectural boundaries.

The best way to review validation placement is by mapping request flows and validating boundary conditions against local documentation. This Skill checks validation placement and error handling across domain, app, HTTP, and infra layers.

Yes, this boundary enforcement approach works for refactoring existing codebases by reviewing dependency direction and type ownership. It requires adherence to local documentation and a defined workflow for mapping request flows during the refactoring process.

You should never bypass architectural boundaries when introducing a new API endpoint, as it causes code tangling. Use boundary enforcement to verify that request DTOs, validation, and authentication logic remain correctly separated across layers.