菜单
Reusable NixOS, Home Manager, and flake configuration patterns. Use when planner or implementer needs proven directory structures, module split patterns, host layouts, secrets organization, overlays, or template-style examples instead of abstract explanation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Entry skill for `.codex` collaboration. Read the role-specific manual for your current client.
Use this skill when the user asks for Nix, Nixpkgs, or NixOS knowledge from local documentation mirrors in this workspace. Start with the high-priority flakes-book branch for practical NixOS and Flakes workflows, then fall back to the official manuals, the NixOS options/module corpus, and the small supplemental wiki navigation branch.
NixOS and Nix flake development for multi-repo architectures, airgapped deployments, and K3s infrastructure. Use when working with flake.nix files, NixOS modules, derivations, devShells, overlays, OCI image packaging, or composing multiple flake repositories. Covers Nix language syntax, flake inputs/outputs, nixosModules exports, stdenv.mkDerivation, and home-manager integration.
Verify whether a NixOS option, Home Manager option, nixpkgs package, module, or attr path actually exists. Use local nix commands and ripgrep instead of guessing.
Minimal tmux runner for one task per session. Use when Codex needs to create an isolated tmux session, send commands into that session's main shell, inspect the session status, or inspect recent output from the main window.
Use when adding, removing, renaming, reorganizing, or documenting large skill knowledge bases or template libraries in this repository, especially nixos-knowledge-base and nixos-patterns.
| name | nixos-patterns |
| description | Reusable NixOS, Home Manager, and flake configuration patterns. Use when planner or implementer needs proven directory structures, module split patterns, host layouts, secrets organization, overlays, or template-style examples instead of abstract explanation. |
Use this skill when the task is not "does this exist in nixpkgs?" but "what is a strong way to structure this configuration?"
nixos for conceptual explanation.nixpkgs-inspector when existence or definition location must be verified..
|-- SKILL.md
`-- templates/
|-- README.md
|-- nixos-classic-starter/
|-- nixos-flake-starter/
|-- luo216-nix-config/
|-- ryan4yin-nix-config/
|-- ryan4yin-nix-config-dma-shell/
|-- ryan4yin-nix-config-i3-kickstarter/
`-- ryan4yin-nix-config-migrate-idols-ai/
Use templates/ for concrete skeletons and real-world repository examples. Template entry paths are intentionally flat so users can jump straight to the selected starter or reference repo.
templates/README.md
Template storage conventions and current index.