Skip to content
Log in

Module Boundary Review

Draws boundaries along what changes together, rather than along the organisation chart or the technical layer.

0

Share this prompt

Free — no card needed

Create a free account

to open Module Boundary Review — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryCodingForDevelopersTested onClaudeChatGPT

Running it, start to finish

  1. Look at which files actually change together in git history.
  2. Find the cycles and the everything-depends-on-it module.
  3. Move one boundary at a time, shipping each step.

What you get back

The output this produces, every time.

  • Uses what-changes-together as the test, which is what a boundary exists to serve.
  • Identifies layer-based boundaries, where every feature change touches every layer.
  • Accepts that some duplication is correct when two similar things change for different reasons.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Look at your commits. Files that always change together are one thing. That evidence is in git and is more reliable than any architectural intuition.
  • Watch the common package. A shared utilities module everything depends on means every change is a global change, which is the opposite of a boundary.
  • Never restructure big-bang. They get abandoned half-way and leave two conventions in one codebase, which is worse than the original problem.

More Coding prompts

All Coding

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.