Clairvoyance

Name: Clairvoyance
Author: clairvoyance.fyi

MCP serverMCP

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

by clairvoyance.fyirepository ↗homepage ↗v1.3.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"clairvoyance","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability68/68 checks ok

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	158 ms	server fyi.clairvoyance/mcp 1.3.1 · protocol 2025-06-18 · 17 tools
12 h ago	mcp initialize	ok	200	190 ms	server fyi.clairvoyance/mcp 1.3.1 · protocol 2025-06-18 · 17 tools
19 h ago	mcp initialize	ok	200	165 ms	server fyi.clairvoyance/mcp 1.3.1 · protocol 2025-06-18 · 17 tools
26 h ago	mcp initialize	ok	200	161 ms	server fyi.clairvoyance/mcp 1.3.1 · protocol 2025-06-18 · 17 tools
33 h ago	mcp initialize	ok	200	253 ms	server fyi.clairvoyance/mcp 1.3.1 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	226 ms	server fyi.clairvoyance/mcp 1.3.1 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	216 ms	server fyi.clairvoyance/mcp 1.3.1 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	216 ms	server fyi.clairvoyance/mcp 1.3.1 · protocol 2025-06-18 · 17 tools
3 d ago	mcp initialize	ok	200	152 ms	server fyi.clairvoyance/mcp 1.3.1 · protocol 2025-06-18 · 17 tools
3 d ago	mcp initialize	ok	200	236 ms	server fyi.clairvoyance/mcp 1.3.1 · protocol 2025-06-18 · 17 tools

Tools observed via MCP handshake

deep-modules — 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
module-boundaries — 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 mo
information-hiding — Checks for information leakage across module boundaries, including temporal decomposition and false encapsulation. Use when modules change together, implementat
pull-complexity-down — Checks whether complexity is pushed to callers or absorbed by implementations — the direction complexity flows. Use when callers must do significant setup, hand
general-vs-special — Evaluates whether interfaces are appropriately general-purpose. Use when checking interface generality, when if-branches or parameters serve only one caller, or
error-design — Reviews error handling and exception design, applying the "define errors out of existence" principle. Use when reviewing error handling, when a module throws to
abstraction-quality — Evaluates whether abstractions provide a genuinely different way of thinking or are structurally shallow. Use when adjacent layers feel redundant, wrappers add
naming-obviousness — Reviews naming quality and code obviousness via the isolation test, scope-length principle, and consistency audit. Use when names feel vague, something is hard
comments-docs — Reviews comment quality and documentation practices: the four comment types, comments-first workflow, and comment rot. Use when reviewing comments or docs, when
strategic-mindset — Assesses whether code reflects strategic or tactical thinking, including the 10-20% investment rule and tactical-tornado patterns. Use when evaluating design in
design-it-twice — Generates and compares at least two fundamentally different design alternatives on concrete criteria before committing. Use when the user asks to design somethi
code-evolution — 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
complexity-recognition — 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
red-flags — 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
design-review — 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 ask
diagnose — 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 ski
fetch-reference — Fetch a supporting file from a Clairvoyance skill's references/ folder, when the skill's instructions point to one. Available: information-hiding (back-door-lea

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

software-designcode-reviewagent-skills

kind ARD catalog (/.well-known/ard.json)

name ARD catalog (/.well-known/ard.json)

repoUrl ARD catalog (/.well-known/ard.json)

summary ARD catalog (/.well-known/ard.json)

version ARD catalog (/.well-known/ard.json)

description ARD catalog (/.well-known/ard.json)

homepageUrl ARD catalog (/.well-known/ard.json)

publisherUrl ARD catalog (/.well-known/ard.json)

publisherName ARD catalog (/.well-known/ard.json)

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

ARD catalog (/.well-known/ard.json)urn:air:clairvoyance.fyi:mcp:clairvoyance

first seen 19 d ago · fetched 19 d agoopen ↗

Official MCP Registryfyi.clairvoyance/mcp

first seen 19 d ago · fetched 3 d agoopen ↗

Field history (9 recent events)

19 d ago · declared · publisherName → "clairvoyance.fyi"
19 d ago · declared · publisherUrl → "https://clairvoyance.fyi"
19 d ago · declared · publisherName → "fyi.clairvoyance"
19 d ago · declared · homepageUrl → "https://clairvoyance.fyi/mcp"
19 d ago · declared · summary → "Software design skills for AI coding agents, inspired by A Philosophy of Software Design."
19 d ago · declared · version → "1.3.1"
19 d ago · declared · protocols → ["mcp"]
19 d ago · declared · repoUrl → "https://github.com/codybrom/clairvoyance"
19 d ago · declared · description → "Software design skills for AI coding agents, inspired by A Philosophy of Software Design."

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from