The Clairvoyance MCP server,
connected in one click.

deep-modules — Measures module depth: whether the interface is simple relative to the implementation behind it. Use when an interface has too many paramete

module-boundaries — Evaluates where module boundaries are drawn and whether modules should be merged or split. Use when deciding whether to combine or separate

information-hiding — Checks for information leakage across module boundaries, including temporal decomposition and false encapsulation. Use when modules change t

pull-complexity-down — Checks whether complexity is pushed to callers or absorbed by implementations — the direction complexity flows. Use when callers must do sig

general-vs-special — Evaluates whether interfaces are appropriately general-purpose. Use when checking interface generality, when if-branches or parameters serve

error-design — Reviews error handling and exception design, applying the "define errors out of existence" principle. Use when reviewing error handling, whe

abstraction-quality — Evaluates whether abstractions provide a genuinely different way of thinking or are structurally shallow. Use when adjacent layers feel redu

naming-obviousness — Reviews naming quality and code obviousness via the isolation test, scope-length principle, and consistency audit. Use when names feel vague