I set up a 34-table demo store with one circular dependency in it, on purpose. Schemity's Context Map found ten.
No table has a prefix, so nothing in the names says which module it belongs to. I asked Claude Code to group the tables by domain through the MCP server of Schemity, the desktop database design software I build. One request gave seven legends, and Sync from legends turned each into a context view.
The Context Map then listed the cycles between those domains. All ten run through shipping.
The one I planted was users and addresses. The other nine came from foreign keys I had written without thinking about modules, like stock_levels pointing at warehouses.
https://schemity.com/blog/reverse-engineer-legacy-database-group-by-domain/

schemity.comReverse Engineering a Legacy Database: Let an AI Agent Group the ERD by Domain - SchemityA reverse engineered ERD shows every table and no domains, because the domains live in the code. Schemity lets an AI agent read that code, group the diagram into legends over MCP, and hand you each step to review.
commit 33beec5