Skill Claude CodeCodex
Synthesize multiple papers, benchmarks, interviews, reviews, or other sources into a defensible and qualified conclusion. Use for conflicting evidence, literature synthesis, claim auditing, argument mapping, qualitative coding, belief updates, or any request that must expose counter-evidence, uncertainty, and source…
Skill Claude CodeCodex
Draw the line where it costs least. Use for build-vs-buy calls, "where does this module/team/service boundary belong?", APIs and abstractions forcing users into implementation vocabulary, tools that should augment rather than automate, hardcoded decisions that belong at runtime, or information nobody can find.
Skill Claude CodeCodex
Correlation walked in; make it prove causation. Use when someone claims "X causes Y" from observational data, asks "did the change actually cause the improvement?", "is this confounded?", "what would have happened if we hadn't shipped it?", plans an A/B test, or investigates why an incident/outbreak spread the way it…
Skill Claude CodeCodex
Audit the decision before it ships. Use for "are we sure about this?", high-stakes choices made on fast intuition, plans with no failure scenario, estimates that are suspiciously optimistic, metrics being gamed (Goodhart), unfalsifiable claims, negotiation prep, or strategies that break in extreme conditions.
Skill Claude CodeCodex
Bound it before you build it. Use when a decision is blocked by "we don't have data", an estimate looks suspiciously precise, someone asks "is this even feasible?", "how much capacity do we need?", "will this scale?", or a claimed number has never been cross-checked by a second method.
Skill Claude CodeCodex
The artifact is correct and nobody can use, learn, or read it. Use when every component metric is green but the end-to-end experience is broken, when onboarding is too slow or documentation goes unread, when the observer is inside the system being studied (UX research, dogfooding), or when code is right but unreadable…
Skill Claude CodeCodex
Read the wreckage before rebuilding. Use for incident post-mortems, "what happens when everything goes wrong at once?", flaky or anomalous cases being filtered out as noise, "that's weird" moments nobody wrote down, oscillating or unstable feedback behavior, and designs whose only failure mode is crash.
Skill Claude CodeCodex
Prove it, don't test-and-hope. Use for concurrent or distributed code with no written spec, "how do we know this is correct?", interfaces that break when implementations are swapped, correctness argued by walking through example traces, wall-clock time used for ordering, or "can this be decided at all?".
Skill Claude CodeCodex
Fix the instrument before trusting the number. Use when someone says "the metric improved but I don't trust it", "measured more than the parts predict", "we want to improve X but nothing reads X", "the numbers don't add up", "requests/money/time are disappearing", or a measurement may perturb the system it measures.
Skill Claude CodeCodex
Some questions are "what happened and what did it mean", not "what is the mechanism". Use when an account must be reconstructed rather than measured, when a sequential process has a missing or out-of-order step, when a story is told to explain a failure, or when a claim sounds authoritative but may be structurally…
Skill Claude CodeCodex
Legitimacy is a design property, not an afterthought. Use when a rule, policy, or allocation must be written or applied and the open question is "is this fair and consistently applied?" rather than "does it work", when a general rule does not determine a specific case, when harm emerged with nobody having decided it…
Skill Claude CodeCodex
The question itself may be the bug. Use when a debate goes in circles, both options of a binary feel wrong, improving one parameter degrades another, "we're stuck" on a problem that resists direct attack, a metaphor is doing hidden work in the architecture, or a trade-off is being denied rather than made.
Skill Claude CodeCodex
When the notation is the obstacle and the option space was never enumerated. Use when the current vocabulary hides the solution, when a system claims to be exhaustive but nobody checked whether the space is searchable, when a forecast is too narrow because no one pushed the principle to its limit, or when you need the…
Skill Claude CodeCodex
Find the hidden pattern that organizes the mess. Use for "these look related but we can't say how", classification with suspicious gaps, reverse-engineering an undocumented system or format, "is there a symmetry we're not using?", scale-free or fat-tailed data, or generating conjectures from computed special cases.
Skill Claude CodeCodex
Find where a small push changes the whole system. Use when local fixes keep failing, "where should we intervene?", recurring organizational patterns (shifting the burden, escalation, tragedy of the commons), behavior driven by stocks/flows/delays, adoption stalling, or shared resources being depleted.
Plugin Claude Code
Plugin marketplace listing 1 plugin: hypermnesia-mcp-viz.
Plugin Claude Code
Standalone visualization MCP for Cortex — a live neural-graph galaxy of every project, file, symbol, memory, discussion and wiki page, plus a per-session execution trace. Read-only bridge over Cortex's shared PostgreSQL and the /.claude artifacts.
Instructions file
Instructions for cdeust/cortex-viz, covering cortex-viz, repo-specific constraints and etiquette.
Hook
Runs after a tool call finishes, executing activity_capture.py via python3. From cdeust/cortex-viz.
Hook
Runs when you submit a prompt, before the agent sees it, executing activity_capture.py via python3. From cdeust/cortex-viz.
Skill Claude CodeCodex
Launch the interactive Cortex neural-graph visualization (the hypermnesia-mcp-viz MCP). Use when the user says 'show visualization', 'show me the graph', 'visualize memories', 'show memory map', 'open neural graph', 'cortex-visualize', or when a visual overview of the memory system, codebase graph, or session trace…
MCP server Claude CodeCodexCursor +2
Visualization and graph MCP server for Cortex — neural graph, methodology map, workflow graph, and trace UI extracted from the Cortex memory engine. Runs locally from the hypermnesia-mcp-viz Python package.
cdeust/ai-architect-mcp-codebase
Plugin Claude Code
Plugin marketplace listing 1 plugin: ai-architect-mcp-codebase.
cdeust/ai-architect-mcp-codebase
Plugin Claude Code
Rust MCP server that indexes ANY codebase into a LadybugDB property graph — source in 11 languages with full AST, plus docs/config/binaries as File nodes (.js→Imports, Markdown→References). Resolves imports and call chains, detects communities via Leiden, traces execution flows from entry points, and exposes 26 MCP…