module-secret-auditor

Use when creating new modules or directories, drawing or questioning module boundaries, when a change ripples across 3+ directories, or when the user asks "where should this code live?" or "how should I structure this?". Trigger on structural decisions and reorganizations. NOT for a module doing too many unrelated things (cohesion-analyzer), domain-language boundaries (bounded-context-auditor), naming conventions,…