Skill Claude CodeCodex
Model adversarial users, attackers, malformed inputs, prompt injection, abuse cases, and metric gaming.
Skill Claude CodeCodex
Model adversarial users, attackers, malformed inputs, prompt injection, abuse cases, and metric gaming.
Skill Claude CodeCodex
Check whether APIs, CLIs, and UIs make the right actions obvious and wrong actions hard.
Skill Claude CodeCodex
Apply Talebian reasoning to software. expose fragility, tail risk, false confidence, harmful intervention, and opportunities for via negativa, optionality, barbell design, and antifragile feedback.
Skill Claude CodeCodex
Treat deliberate deletion as a healthy biological function. Apply apoptosis vs necrosis, autophagy, senescence, and the principle that not-dying is pathological to deprecation, sunsetting, and pruning.
Skill Claude CodeCodex
Surface hidden assumptions in code, specs, designs, and debugging plans; classify which are guaranteed, validated, trusted, inherited, or unsafe.
Skill Claude CodeCodex
Review notifications, prompts, logs, errors, and UI signals for salience, interruption cost, and prioritization.
Skill Claude CodeCodex
Update beliefs about bugs, hypotheses, and triage decisions using priors, likelihoods, and posteriors rather than gut anchoring on the latest piece of evidence.
Skill Claude CodeCodex
Check reasoning for anchoring, confirmation bias, availability bias, sunk-cost fallacy, and premature closure.
Skill Claude CodeCodex
Behavioral finance applied to tech adoption — recognize hype cycles, herding, FOMO, and Minsky moments before deciding to chase the next framework, paradigm, or migration.
Skill Claude CodeCodex
Decide where to spend engineering effort across competing demands using ROI, hurdle rates, opportunity cost, and zero-based budgeting — and ignore sunk cost.
Skill Claude CodeCodex
Reconstruct timelines and causal chains from logs, stack traces, commits, artifacts, tests, and changed files before deciding what happened.
Skill Claude CodeCodex
Improve readability, conceptual flow, naming, API story, and maintainability of complex code.
Skill Claude CodeCodex
Evaluate code, APIs, docs, and workflows for working-memory burden, chunking, naming, and mental model fit.
Skill Claude CodeCodex
Apply engineering bring-up and tear-down protocols (FAT, SAT, punchlist, LOTO, mothballing) to service launches and sunsets so systems start clean and end cleanly.
Skill Claude CodeCodex
Grice's maxims and speech act theory applied to engineering text — error messages, commit messages, log lines, prompts, and PR descriptions. Distinguishes literal meaning from intended effect.
Skill Claude CodeCodex
Find the current bottleneck, avoid optimizing non-constraints, and reason about throughput and queues.
Skill Claude CodeCodex
Apply epidemiological reasoning — R0, generation time, susceptibility, contact tracing, herd immunity — to vulnerability propagation, dependency CVEs, credential leaks, bug spread, and incident blast radius.
Skill Claude CodeCodex
PID controllers and classical control theory applied to autoscalers, congestion control, rate limiters, and any feedback-driven regulator. Use when a system must drive a measured variable to a setpoint without oscillating, overshooting, or stalling.
Skill Claude CodeCodex
Use nucleation, supersaturation, and crystal growth to reason about standards adoption, pattern propagation, and why some ideas suddenly "take" while others remain dissolved.
Skill Claude CodeCodex
Use differential diagnosis to triage possible causes by likelihood, severity, and test cost.
Skill Claude CodeCodex
Track units of measure across code, APIs, and data so unit-mismatch operations are caught at the type, spec, or review level rather than at runtime.
Skill Claude CodeCodex
Analyze how knowledge is shared across code, docs, tools, tests, teams, and rituals.
Skill Claude CodeCodex
Look for emergent behavior where simple local rules produce surprising global effects.
Skill Claude CodeCodex
Act as a senior engineering coach. Review an engineer's recent work across PRs, code reviews, issues, and commits; produce an evidence-cited SWOT and a short list of prioritized, behavioural actions — with room for the engineer to add context and challenge findings.