Skill Claude CodeCodex
Apply thermodynamic reasoning — entropy, free energy, reversibility — to codebase decay, tech debt, drift, and the cost of maintenance.
2 3mo ago A 35 tokens
Skill Claude CodeCodex
Reason about absolute and relative error, floating-point precision, condition numbers, and accumulated error in iterative methods, money, timestamps, geo, and ML pipelines.
2 3mo ago A 38 tokens
Skill Claude CodeCodex
Apply natural selection thinking to API and codebase evolution — what is being selected for, what drifts, what persists vestigially, and where the system sits on its fitness landscape.
2 3mo ago A 42 tokens
Skill Claude CodeCodex
Designed margin against expected load, applied to capacity, retries, rate limits, and headroom decisions. Use when deciding "how much buffer is enough" for a system that must not fail under realistic peaks.
2 3mo ago A 46 tokens
Skill Claude CodeCodex
Enumerate failure modes, effects, severity, detectability, and mitigations before risky changes.
2 3mo ago A 24 tokens
Skill Claude CodeCodex
Cyclic loading failure below yield strength, applied to systems that work fine for years until they suddenly do not. Use when intermittent sub-threshold stress accumulates damage that single-event analysis misses.
2 3mo ago A 47 tokens
Skill Claude CodeCodex
Analyze retries, queues, rate limits, cancellations, streaming, and reactive loops for stability.
2 3mo ago A 22 tokens
Skill Claude CodeCodex
Order-of-magnitude back-of-envelope reasoning for capacity, latency, cost, and feasibility — before optimizing or designing.
2 3mo ago A 28 tokens
Skill Claude CodeCodex
Reason about iterative systems — retries, type checkers, schedulers, autoscalers, eventual consistency, dataflow — using fixed points, convergence, and contraction.
2 3mo ago A 39 tokens
Skill Claude CodeCodex
Sports technique discipline applied to engineering quality under pressure. Use when deadlines, incidents, or fatigue threaten the discipline that prevents the next failure.
2 3mo ago A 31 tokens
Skill Claude CodeCodex
Discover system invariants and mathematical properties, then design logical rules that can be verified with assertions, contracts, or tests.
2 3mo ago A 28 tokens
Skill Claude CodeCodex
Risk transfer and pooling — design redundancy, error budgets, multi-region, backups, and on-call as deliberate insurance instruments with explicit premiums.
2 3mo ago A 33 tokens
Skill Claude CodeCodex
Apply immunology to defense system architecture — innate vs adaptive layers, self/non-self discrimination, memory, vaccination, and the cost of overreaction.
2 3mo ago A 33 tokens
Skill Claude CodeCodex
Predict how users, maintainers, systems, and attackers respond to rules, defaults, metrics, and rewards.
2 3mo ago A 27 tokens
Skill Claude CodeCodex
Perform blameless incident analysis focused on contributing factors, safeguards, and recurrence prevention.
2 3mo ago A 20 tokens
Skill Claude CodeCodex
Analyze loss, noise, ambiguity, compression, redundancy, and propagation of information across a system.
2 3mo ago A 23 tokens
Skill Claude CodeCodex
Hermeneutics for code, specs, PRs, and error messages — the disciplined practice of charitable interpretation, the hermeneutic circle, and distinguishing reading-out from reading-in.
2 3mo ago A 42 tokens
Skill Claude CodeCodex
Reconcile state transitions so every acquire/release, enqueue/dequeue, event/source, and resource/owner pair balances.
2 3mo ago A 28 tokens
Skill Claude CodeCodex
Queueing-theory reasoning for latency, throughput, and utilization. Use when sizing pools, diagnosing tail latency, or trading off concurrency vs response time using L = λW and the utilization/latency curve.
2 3mo ago A 50 tokens
Skill Claude CodeCodex
Choose a strategic maintenance posture (reactive, preventive, predictive, RCM) per subsystem using MTBF, MTTR, criticality, and the bathtub curve — not by default or hype.
2 3mo ago A 44 tokens
Skill Claude CodeCodex
Apply order-book mechanics — bid/ask, queue position, latency arbitrage, batch vs continuous matching — to schedulers, load balancers, and any system that matches supply to demand.
2 3mo ago A 43 tokens
Skill Claude CodeCodex
Choose tech stack, libraries, and tools by property fit using required-vs-desirable specs, weighted decision matrices, Ashby-style trade-off plots, and lifecycle cost — not hype.
2 3mo ago A 40 tokens
Skill Claude CodeCodex
Design rules, APIs, quotas, and protocols so the dominant strategy of self-interested participants is the cooperative one. Use when an interface will be used by parties who optimise their own metric and your job is to make the system robust to that.
2 3mo ago A 53 tokens
Skill Claude CodeCodex
Compare the system model, developer model, and user model; identify mismatches that cause bugs or UX confusion.
2 3mo ago A 27 tokens