Convert Nix flakes to modular flake-parts structures with perSystem outputs.
npx skills add https://github.com/Omegaice/dotfiles --skill using-flake-parts
Please help me install this Agent Skill. Skill: using-flake-parts Source: https://github.com/Omegaice/dotfiles/tree/main/.claude/skills/using-flake-parts Command: npx skills add https://github.com/Omegaice/dotfiles --skill using-flake-parts
Nix flakes can become complex and boilerplate-heavy, especially when managing configurations across multiple systems. This Skill provides expert guidance on the flake-parts framework, simplifying modular organization, reducing duplication, and automating multi-system builds.
flake-parts for clarity, reusability, and maintainability, eliminating common boilerplate.perSystem, and flake-parts automatically generates them for all specified target architectures.easyOverlay module to automatically generate Nixpkgs overlays from your perSystem packages, ensuring proper dependency resolution.flake-parts structure. This allows you to define a new package once, and have it automatically built and available for both your x86_64-linux desktop and aarch64-linux server, saving significant configuration time.Explain how to convert a standard Nix flake to use the flake-parts framework, focusing on moving packages and devShells into perSystem.
High-intent search queries and answers about installing and using this skill.
Converting to flake-parts involves moving your packages and devShells into perSystem blocks, which automatically generates outputs for all specified target systems. Define each package once in perSystem, and flake-parts handles multi-system builds without duplicating configuration.
Flake-parts is a framework that simplifies organizing complex Nix flakes by reducing boilerplate and enabling modular configuration. It automatically builds packages for multiple architectures like x86_64-linux and aarch64-linux from a single definition, eliminating manual duplication.
The easyOverlay module automatically generates Nixpkgs overlays from your perSystem packages, ensuring proper dependency resolution across systems. This eliminates manual overlay management and keeps package definitions synchronized.
Yes. Flake-parts provides reusable flakeModules and mkFlake composition to structure modular configurations. You can organize overlays, partitions, and multi-system deployments while maintaining clarity and reducing configuration duplication.
Familiarity with Nix flakes, perSystem outputs, and basic Nixos configuration is required. Understanding of module arguments, importApply semantics, and standard flake structure helps you leverage flake-parts' modular features effectively.
Flake-parts includes debug mode to troubleshoot perSystem outputs, mkFlake composition, and module argument resolution. Use this to identify issues with partition organization or overlay dependencies before deployment.
olafkfreundConfigure reproducible NixOS dev shells with Nix Flakes and direnv.
kettleofketchupManage NixOS configurations and flake-driven workflows across multi-repo architectures.
MultipixeloneGuide Nix flake migration to flake-parts for modular multi-system builds.
cameronraysmithEnforce Nix development conventions for flakes, modules, and platform configurations.