audit-domain

To detect domain logic leaking into routes, an automated audit scans TypeScript files in routes and lib/domain directories to surface boundary validation issues, non-exhaustive switches, and misplaced business logic using ripgrep and Bash scripts.

Boolean flags threaten correct domain modeling by creating ambiguous state representations. An audit surfaces these anti-patterns and recommends explicit discriminated unions or as const enums to enforce strict functional programming discipline and prevent invalid state combinations.

Enforcing ADR compliance involves scanning domain and route TypeScript files against codified ADR-009 and ADR-012 references to detect anti-patterns, generating a guided report that highlights violations and opportunities to move logic into lib/domain.

Auditing boundary-parse enforcement requires a local ripgrep tool (rg) and a Bash helper script included under the skill, meaning no external package dependencies are needed beyond having ripgrep installed in your local environment.

The best way to surface non-exhaustive switches is running an automated domain audit that checks web/src/lib/domain TypeScript files, comparing patterns against baseline references like standings.ts and registration.ts to flag incomplete type handling.

Keeping domain logic out of routes requires scanning for boundary validation issues and logic leakage, then migrating identified business logic into lib/domain modules while ensuring explicit discriminated unions replace boolean flags for proper FP discipline.