Our review
This skill enables NixOS configuration and Nix flake development for multi-repo architectures, airgapped deployments, and K3s infrastructure, providing patterns for composing flakes, modules, derivations, and OCI image packaging.
Strengths
- Comprehensive coverage of NixOS and Nix flake patterns, including multi-repo composition.
- Handles advanced scenarios like airgapped deployments and OCI image packaging.
- Provides efficient patterns for conditional module loading and lazy evaluation.
- Integrates with Kubernetes tooling (Helm, Kustomize) within Nix builds.
Limitations
- Requires substantial Nix language expertise to use effectively.
- The advanced patterns (airgapped, multi-repo) may not be needed for simpler single-machine setups.
- Documentation references are only linked, not embedded, so the user may need to consult additional files.
Use this skill when managing complex NixOS fleets, multiple repos with shared dependencies, or when deploying NixOS to airgapped or K3s environments.
Do not use for simple single-machine NixOS configurations where standard NixOS guides suffice, or if you are new to Nix and need basic setup guidance.
Security analysis
SafeThe skill is a reference document for NixOS development, containing only standard and necessary commands for building, developing, and deploying Nix configurations. No malicious, destructive, or exfiltrating instructions are present.
No concerns found
Examples
Help me set up a Nix flake that depends on an internal Git repository and pins the same nixpkgs version across both repos.Write a Nix derivation that downloads a Docker image and outputs it as an OCI tarball for use in an airgapped environment.Create a NixOS module with an enable option that conditionally loads additional configuration using `lib.mkIf`.name: nixos description: 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.
NixOS Development
Overview
Build and maintain NixOS configurations using Nix flakes. Focus on multi-repo composition, airgapped deployments, and declarative infrastructure.
Quick Reference
| Task | Command |
|------|---------|
| Build package | nix build .#packageName |
| Enter devShell | nix develop |
| Update flake inputs | nix flake update |
| Update single input | nix flake lock --update-input nixpkgs |
| Show flake outputs | nix flake show |
| Check flake | nix flake check |
| Rebuild NixOS | sudo nixos-rebuild switch --flake .#hostname |
| Build ISO | nix build .#nixosConfigurations.iso.config.system.build.isoImage |
Flake Structure
Standard multi-repo flake pattern:
{
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
# Pin dependent flakes to same nixpkgs
other-flake.url = "git+ssh://gitlab.example.com/repo";
other-flake.inputs.nixpkgs.follows = "nixpkgs";
};
outputs = { self, nixpkgs, other-flake, ... }:
let
system = "x86_64-linux";
pkgs = import nixpkgs { inherit system; };
in {
# NixOS system configurations
nixosConfigurations.hostname = nixpkgs.lib.nixosSystem {
inherit system;
modules = [
other-flake.nixosModules.default
./configuration.nix
];
};
# Reusable NixOS modules
nixosModules.default = import ./modules;
# Packages
packages.${system} = { /* ... */ };
# Development shells
devShells.${system}.default = pkgs.mkShell { /* ... */ };
};
}
NixOS Module Pattern
Export modules for composition:
# modules/default.nix
{ config, lib, pkgs, ... }:
{
imports = [ ./service.nix ];
options.myModule.enable = lib.mkEnableOption "my module";
config = lib.mkIf config.myModule.enable {
# configuration here
};
}
OCI Image Packaging
For airgapped deployments, package images as store paths:
# Single image to OCI tarball
imagePackage = pkgs.runCommand "image-name" {
buildInputs = [ pkgs.skopeo ];
} ''
skopeo copy docker://registry/image:tag oci-archive:$out
'';
Helm + Kustomize in Nix
Render manifests at build time:
manifests = pkgs.runCommand "manifests" {
buildInputs = [ pkgs.kubernetes-helm pkgs.kustomize ];
} ''
helm template release ${./chart} --namespace ns > base.yaml
kustomize build ${./overlays} > $out
'';
Detailed References
For comprehensive documentation on specific topics:
| Topic | Reference File |
|-------|----------------|
| Nix language syntax | references/nix-language.md |
| Flake inputs/outputs | references/flakes.md |
| NixOS modules & options | references/nixos-modules.md |
| Packaging & derivations | references/packaging.md |
| DevShells & overlays | references/devshells.md |
| Home Manager | references/home-manager.md |
Common Patterns
Pin nixpkgs across repos
Use inputs.X.inputs.nixpkgs.follows = "nixpkgs" to ensure consistent package versions.
Conditional module loading
imports = lib.optionals config.feature.enable [ ./optional-module.nix ];
Lazy evaluation with mkIf
Always use lib.mkIf for conditional config to avoid infinite recursion:
config = lib.mkIf config.myService.enable { /* ... */ };
Override priorities
lib.mkDefault(priority 1000) - easily overridable defaultslib.mkForce(priority 50) - force value regardless of other definitionslib.mkOverride N- custom priority (lower = higher priority)
Troubleshooting
"error: getting status of '/nix/store/...': No such file or directory"
Missing store path. Run nix build or ensure binary cache is configured.
"error: infinite recursion encountered"
Using config values in imports or not wrapping conditional config in lib.mkIf.
"error: attribute 'X' missing"
Check flake inputs match expected names. Verify follows directives.
Flake not seeing local changes
Run git add . - flakes ignore untracked files.
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.