Skill Claude Code
French culinary preparation discipline applied to risky software operations — stage materials, state, and observers before execution so you never scramble mid-flight.
Skill Claude Code
French culinary preparation discipline applied to risky software operations — stage materials, state, and observers before execution so you never scramble mid-flight.
Skill Claude Code
Apply Toyota Production System poka-yoke — design APIs, configs, and workflows so wrong actions are structurally impossible, not merely detected.
Skill Claude Code
Analyze graph structure, centrality, bottlenecks, dependency risk, critical nodes, and blast radius.
Skill Claude Code
Reason about how the act of observing a system perturbs it — Heisenbugs, probe effect, log-induced timing changes, debugger-only behavior.
Skill Claude Code
Use observe-orient-decide-act loops for fast adaptive work under uncertainty.
Skill Claude Code
Design controlled drills that test assumptions about failure handling, observability, rollback, and recovery.
Skill Claude Code
Real options theory and Bezos's one-way-vs-two-way doors — value the right to decide later as a first-class asset, separate from the decision itself.
Skill Claude Code
Reason about partial orders, joins, meets, and monotonicity to design type lattices, CRDTs, version compatibility, permission models, and dataflow analyses.
Skill Claude Code
Apply endurance pacing — lactate threshold, glycogen budget, negative split, fueling — to sustainable engineering rate, sprint cadence, and avoiding mid-quarter exhaustion.
Skill Claude Code
Apply training periodization — macrocycle/mesocycle/microcycle, taper, supercompensation, polarized training — to release cadence, planned slack, and post-launch recovery.
Skill Claude Code
Apply pharmacology — dose-response, therapeutic window, half-life, titration, interactions — to system parameter changes, rollouts, and tuning.
Skill Claude Code
Converting perishable to stable forms — the discipline of snapshots, immutable archives, frozen schemas, and pinned versions, with awareness of what is lost in preservation.
Skill Claude Code
Structured debugging methodology based on Popperian falsificationism. Use when stuck on a bug, facing a confusing failure, or when initial debugging attempts haven't worked.
Skill Claude Code
Apply Markowitz mean-variance portfolio theory to technical bets — diversify across uncorrelated risks rather than stacking many bets of the same kind.
Skill Claude Code
Create operational checklists for risky changes, launches, migrations, and incident prevention.
Skill Claude Code
Gary Klein's prospective hindsight — imagine the project has already failed and work backwards to identify the causes, before committing.
Skill Claude Code
Apply strength-training principles — SAID, dose-response, supercompensation, accommodation, GAS — to capacity, load testing, chaos engineering, and adaptive resilience.
Skill Claude Code
Apply mathematical proof techniques — induction, contradiction, contrapositive, cases, construction — to argue about loop invariants, recursion termination, exhaustiveness, and edge cases.
Skill Claude Code
Apply chemical kinetics — rate laws, activation energy, catalysis, equilibrium, Le Chatelier — to systemic adoption, throughput, and process flow.
Skill Claude Code
Real-time triage during execution failures — chef's instincts for which broken dishes can be saved, which must be abandoned, and which adjustments make things worse.
Skill Claude Code
Apply special-relativistic intuitions and Lamport's logical-time framework to reason about causality, ordering, and consistency in distributed systems.
Skill Claude Code
Design systems to degrade gracefully, recover, absorb shocks, and maintain safety under stress.
Skill Claude Code
Disciplined understanding of opaque systems through black/gray/white-box analysis, behavioral characterization, golden references, and differential analysis — separating observed behavior from inferred contract.
Skill Claude Code
Apply art-conservation discipline — minimum intervention, reversibility, distinguishing original from accreted material, documenting before changing — to refactors, migrations, schema changes, and any edit to code you do not fully understand.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: