Clairvoyance

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

Software design skills for AI coding agents, inspired by A Philosophy of Software Design.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Clairvoyance": {
      "url": "https://clairvoyance.fyi/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (17)

• deep-modules read-only

  Measures module depth: whether the interface is simple relative to the implementation behind it. Use when an interface has too many parameters or methods, many small classes each do too little, or methods just forward calls. Not for whether adjacent layers provide different abstractions (use abstraction-quality) or merging/splitting modules (use module-boundaries).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• module-boundaries read-only

  Evaluates where module boundaries are drawn and whether modules should be merged or split. Use when deciding whether to combine or separate two modules, when modules are tightly coupled, or when a change to one forces changes to another. Not for depth within a single module (use deep-modules) or abstraction-layer quality (use abstraction-quality).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• information-hiding read-only

  Checks for information leakage across module boundaries, including temporal decomposition and false encapsulation. Use when modules change together, implementation details leak across boundaries, or structure follows execution order rather than knowledge ownership. Not for merge/split decisions (use module-boundaries) or interfaces over-specialized for one caller (use general-vs-special).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• pull-complexity-down read-only

  Checks whether complexity is pushed to callers or absorbed by implementations — the direction complexity flows. Use when callers must do significant setup, handle errors the module could resolve, or configure things they don't understand. Not for module depth (use deep-modules), knowledge leakage (use information-hiding), or exception strategy once an error must surface (use error-design).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• general-vs-special read-only

  Evaluates whether interfaces are appropriately general-purpose. Use when checking interface generality, when if-branches or parameters serve only one caller, or when getters/setters expose internal representation. Not for information leakage across boundaries (use information-hiding) or auditing configuration parameters (use pull-complexity-down).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• error-design read-only

  Reviews error handling and exception design, applying the "define errors out of existence" principle. Use when reviewing error handling, when a module throws too many exceptions, or when callers must handle errors they shouldn't need to know about. Not for general caller-burden complexity (use pull-complexity-down); this skill is specifically for exception and error-condition strategy.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• abstraction-quality read-only

  Evaluates whether abstractions provide a genuinely different way of thinking or are structurally shallow. Use when adjacent layers feel redundant, wrappers add boilerplate without depth, or an abstraction feels leaky. Not for a single module's interface-to-implementation ratio (use deep-modules) or information leakage across boundaries (use information-hiding).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• naming-obviousness read-only

  Reviews naming quality and code obviousness via the isolation test, scope-length principle, and consistency audit. Use when names feel vague, something is hard to name (a design signal, not a vocabulary problem), or behavior isn't obvious on first read. Not for comment quality or documentation (use comments-docs).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• comments-docs read-only

  Reviews comment quality and documentation practices: the four comment types, comments-first workflow, and comment rot. Use when reviewing comments or docs, when comments just repeat the code, or when something is hard to describe in a sentence. Not for naming or code obviousness (use naming-obviousness).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• strategic-mindset read-only

  Assesses whether code reflects strategic or tactical thinking, including the 10-20% investment rule and tactical-tornado patterns. Use when evaluating design investment, when code was written under time pressure, or when working code consistently degrades the system. Not for judging whether a specific diff looks designed-in or bolted-on (use code-evolution).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• design-it-twice read-only

  Generates and compares at least two fundamentally different design alternatives on concrete criteria before committing. Use when the user asks to design something twice, or before committing to any significant design of classes, modules, APIs, or architecture. Also use when asked how to structure or architect a feature, or when writing the design or alternatives section of an RFC, design doc, or ADR. Not for judging strategic vs. tactical investment in existing code (use strategic-mindset) or whether a change degrades design (use code-evolution).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• code-evolution read-only

  Evaluates whether changes to existing code maintain or degrade design quality. Use when the user asks to review a diff or PR (for example before merging it), or asks about recently modified files, to judge whether each change looks designed-in or bolted-on. Not for scanning design smells (use red-flags) or assessing overall design investment (use strategic-mindset).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• complexity-recognition read-only

  Diagnoses whether complexity exists and where it comes from, using the three-symptom, two-root-cause framework. Use when code feels harder to work with than it should but the specific problem is unclear. Not for scanning known design smells (use red-flags) or evaluating a module's depth (use deep-modules).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• red-flags read-only

  Scans code against 17 design smells (the book's 14 named Red Flags plus 3 process-stage signals) and produces a structured diagnostic report. Use when the user asks for a red flags or design smell scan, asks to check code against a checklist, is evaluating unfamiliar code, or asks open-endedly whether anything is off in a named or pasted file, class, or function, or asks you to look it over. Not for a specific bug, error, or failing test the user has already identified. Not for a plain diff or PR review before merge, or whether a PR maintains design trajectory (use code-evolution for both), or diagnosing why code feels complex (use complexity-recognition).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• design-review read-only

  Orchestrates a structured design review, running the other skills as a diagnostic funnel from complexity triage to a full red-flags sweep. Use when the user asks for a comprehensive or prioritized design assessment of a file, module, or PR. Not for an open-ended "anything off here?" or "take a look at this" prompt that names no review goal (use red-flags), a plain diff review before merge or analyzing how code changed over time (use code-evolution), or applying one specific lens (use that skill directly).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• diagnose read-only

  Routes a vague symptom or complaint to the most relevant Clairvoyance skill via a decision tree. Use when someone describes a problem but doesn't know which skill to reach for. Not for a comprehensive review (use design-review) or a checklist scan (use red-flags).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

• fetch-reference read-only

  Fetch a supporting file from a Clairvoyance skill's references/ folder, when the skill's instructions point to one. Available: information-hiding (back-door-leakage.md); pull-complexity-down (configuration-parameter-audit.md); comments-docs (comments-first-workflow.md); design-it-twice (pre-mortem-fallback.md); red-flags (flag-interaction-map.md); design-review (workflow-builder.md).

  Parameters:

  • skill (required) — string — The skill the file belongs to
  • file (required) — string — The file name inside the skill's references/ folder

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world not declared

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.