메뉴
NixOS module conventions: options vs config, auto-discovery, typed options, service families, port claims. Use when adding or editing a module under modules/.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| name | module-conventions |
| description | NixOS module conventions: options vs config, auto-discovery, typed options, service families, port claims. Use when adding or editing a module under modules/. |
Modules declare options and config. Keep each module inert until its enable flag or equivalent activation condition is set. Prefer independent modules picked up through the auto-discovered registry over modules importing each other.
A new module is a directory at modules/<category>/<name>/ with its own
default.nix. The walker in lib/default.nix (see
discoverModules) finds it on the next eval; no registry edit is needed. Nested
sub-modules follow the same shape (modules/services/minecraft/fabric/default.nix
becomes nixosModules.minecraft.fabric). Helper data that lives next to a
module but is not itself a NixOS module belongs in a sibling directory whose
name starts with _, which the walker skips.
Public options should describe the user's domain. Hide storage mechanics behind typed options, generated files, and small adapters. Use broad escape hatches only at true foreign-format boundaries and name that boundary in the description.
Structured config belongs in structured values. Prefer pkgs.formats.*,
freeform submodules, and typed option trees over string fragments that cannot
merge, inspect, or receive mkDefault and mkForce cleanly.
Cross-cutting helpers come through specialArgs.ix or the public flake lib
surface. Avoid relative-up imports that climb across repo layers. Child and
sibling paths inside one package or module directory are fine.
Service families share a runtime module plus variant modules that fill typed slots. Enabling a variant should enable the runtime by default. Mutually exclusive variants should fail loudly through module merging or explicit validation.
Every module that binds a TCP or UDP socket should declare a port claim next to the bind setting or firewall declaration. A duplicate claim in the same namespace is a useful eval-time failure; intentional co-location needs a real namespace boundary or an explicit alternate port.
Modules that manage artifacts should consume catalogs, lockfiles, or caller supplied sources. Presets and examples should read like intent, with local or private artifacts shown only when that is the point of the example.
