Module Boundaries Review Lens

When invoked with $ARGUMENTS, focus the analysis on the specified file or module. Read the target code first, then apply the checks below.

Evaluate where module boundaries are drawn: are related things together and unrelated things apart?

When to Apply

• Deciding whether to split a large class or merge small ones
• When two modules seem tightly coupled
• When a change to one module frequently requires changes to another
• When reviewing a decomposition decision

Core Principles

The Default Instinct Is Wrong

Most developers assume smaller is better, which produces systems full of shallow, pass-through components that increase cognitive load without hiding anything. The right answer is always whichever arrangement results in lower overall system complexity. Not smaller. Not more separated. Simpler.