How does 'inputs' differ from 'inputs'' in this skill?

While 'inputs' refers to the raw flake inputs, 'inputs'' (inputs prime) provides those same inputs with the current system already pre-selected, removing the need for manual system interpolation.

When should I use 'flake' instead of 'perSystem'?

Use 'perSystem' for things that exist on every platform (packages, shells, checks). Use 'flake' for unique, non-system-specific outputs like NixOS or Home Manager configurations.

How can I debug flake-parts issues using Claude?

Claude can guide you through enabling debug mode in your flake and using 'nix repl' to inspect system-specific arguments, option declarations, and evaluated package sets.

What is the primary benefit of using flake-parts?

It applies the NixOS module system to flakes, allowing you to define configurations once in a 'perSystem' block and automatically generate outputs for all target architectures, drastically reducing boilerplate.

Nix Flake-Parts Expert

Name: Nix Flake-Parts Expert
Author: Omegaice

byOmegaice

•

Deployment & DevOps

Streamlines multi-system Nix flake development by implementing the modular flake-parts framework.

About

The Nix Flake-Parts Expert skill provides specialized guidance for using the flake-parts framework to organize and scale Nix flakes. It helps developers apply the NixOS module system to flake configurations, eliminating repetitive boilerplate for multi-system builds. By leveraging perSystem abstractions and advanced module arguments, this skill enables the creation of maintainable, modular, and highly reusable Nix infrastructure for packages, development shells, and system configurations.

Key Features

Automated per-system output generation for packages, apps, and devShells
Expert guidance on mkFlake structure and modular imports
Best practices for flake-to-flake-parts migration and debugging
2 GitHub stars
Advanced argument handling using inputs' and self' for system-specific logic
Automated overlay creation via the easyOverlay module

Use Cases

Managing Nix configurations across multiple architectures like x86_64 and aarch64
Converting complex, monolithic flakes into organized, modular structures
Developing reusable Nix modules and libraries for shared team infrastructure

About

Key Features

Automated per-system output generation for packages, apps, and devShells
Expert guidance on mkFlake structure and modular imports
Best practices for flake-to-flake-parts migration and debugging
2 GitHub stars
Advanced argument handling using inputs' and self' for system-specific logic
Automated overlay creation via the easyOverlay module

Use Cases

Managing Nix configurations across multiple architectures like x86_64 and aarch64
Converting complex, monolithic flakes into organized, modular structures
Developing reusable Nix modules and libraries for shared team infrastructure