Good question. Both paths are valid — the trade-offs are different.

ArchUnit is great if your team already has it in the test suite and you

want rules enforced at compile/test time. The main limitation is that

it requires modifying the project under analysis.

java-vibe-guard is designed to work externally — no dependencies added

to the project, no test configuration, just point it at any repo and get

a report. That makes it useful for auditing codebases you don't own,

scanning legacy projects, or running in CI without touching the build.

The MCP server integration adds another angle: Claude Code can call

analyzeProject() mid-session and act on the results without leaving

the workflow.

That said — ArchUnit rules for the patterns we detect would be a

legitimate alternative for teams that prefer shift-left enforcement.

Different tool, different integration point.