Menu
The craft bar and defaults for every change: clear ownership, typed boundaries, checked defaults, root-cause fixes, no silent fallbacks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | craft-standard |
| description | The craft bar and defaults for every change: clear ownership, typed boundaries, checked defaults, root-cause fixes, no silent fallbacks. |
Write for the next reader. Pick the simplest design that makes the owner obvious: small named helpers, typed boundaries, no anonymous blobs or copy-pasted orchestration. DRY one domain fact, but do not force an abstraction over genuinely different behavior. Own domain logic once in Rust; bindings (Python, Wasm, FFI) stay thin and logic-free.
Defaults are checked, typed, reproducible, secret- and network-conservative, and overridable with a named reason. Prefer the future-correct interface over a compatibility layer, and delete the code it obsoletes in the same change.
Reject fallbacks: a missing owner, route, config, schema, or transport returns a typed, observable error, never a guessed default, sentinel, or silent retry. Fix root causes at the owner: when an adapter, conversion, or fallback recurs, move the invariant to the boundary that owns it.
Lint failures and repo rules are binding. Bypass only with local evidence, kept small, reason next to the line. Before rebuilding what the ecosystem already provides, push back once: name the tool, the cost, and the gap; when you present a choice, name the recommended default.
A fix lands code plus the nearest durable test; diagnosis alone is unfinished. Tests defend behavior that crosses a boundary, not implementation trivia.
Rust house style for repo-owned crates: edition 2024, naming, module layout, unsafe validation (Miri/loom/shuttle), mutation testing, fuzzing. Use when writing or reviewing Rust.
Use this skill to interactively debug Antithesis test runs using the multiverse debugger. Open a debugging-session URL, inspect container filesystems and runtime state, run shell commands, and extract evidence from inside the Antithesis environment. Supports both the simplified debugger (default) and the advanced notebook mode.
Search across all timelines in an Antithesis test run to find events, correlate property failures, and answer temporal questions about ordering and causation (e.g., did event A always precede failure B? do failures occur even without a preceding fault?).
Cross-cutting facts and gotchas for any Antithesis work on the ix repo — credentials, harness structure, `setup_complete` protocol, assertion idioms, randomness rules, workload design, triage via `agent-browser`, signed report URLs, and Test Composer script placement. Loads whenever an Antithesis run, report, property/assertion, `snouty` invocation, or `antithesis_sdk::` call is in play. Complements the task-scoped `antithesis-{setup,workload, launch,triage,debug,query-logs,research,documentation}` skills.
Triage Antithesis test reports to understand what happened in a run: look up runs, check status, investigate failed properties (assertions), view metadata, download logs, inspect findings, and examine environmental details. Load after a run completes or when investigating a failure.
Autonomously drive a pull request to merged by spawning a background subagent (the fork) that watches CI fail-fast, fixes each failure on the PR branch, re-pushes, and merges when green, all without blocking the main session. Use when the user wants to watch and merge a PR, babysit it, fix CI and merge, get a PR in, or otherwise hand off a PR's CI-to-merge loop so they can keep working. The skill never blocks the main thread; it launches the watcher and returns immediately.
