Organize multi-class Nix configurations into flake-parts modules by feature.
npx skills add https://github.com/sebnow/configs --skill dendritic-nix
Please help me install this Agent Skill. Skill: dendritic-nix Source: https://github.com/sebnow/configs/tree/main/home-manager/agentic/skills/dendritic-nix Command: npx skills add https://github.com/sebnow/configs --skill dendritic-nix
Use the Dendritic Pattern to organize Nix configurations by feature across multiple classes, ensuring every file is a flake-parts module and reducing cross-class duplication.
Add a feature file under modules/ and wire it to all classes via config.flake.modules.
High-intent search queries and answers about installing and using this skill.
Organize Nix configurations by placing each feature in a separate flake-parts module file under modules/, using the deferredModule type to merge contributions across NixOS, home-manager, and nix-darwin classes. This structure reduces cross-class duplication while maintaining predictable merges.
The Dendritic Pattern structures Nix flakes by feature rather than class, ensuring every file is a flake-parts module. A top-level flake.nix imports these modules using import-tree, allowing a single feature to span multiple hosting configurations.
Share Nix module values across classes by using let bindings and flake-parts options instead of specialArgs. This approach ensures clean, predictable merges when configurations are combined via the deferredModule type.
Yes, flake-parts manages multi-host setups by treating each file in the modules directory as a module. Automated imports wire features to all classes via config.flake.modules, enabling shared configurations across NixOS, home-manager, and darwin targets.
Add a new feature by creating a feature file under the modules/ directory and wiring it to all target classes via config.flake.modules. The top-level flake.nix automatically imports it using import-tree, integrating it into the existing NixOS, home-manager, or darwin setup.
Using deferredModule for Nix configuration management requires adherence to flake-parts module architecture and import-tree for file loading. It is specifically designed for feature-based organization across NixOS, home-manager, and nix-darwin, meaning configurations outside this ecosystem are not supported.
darkmatterReorganize Nix flake layouts into thin public APIs and feature-oriented src paths.
aytordevGenerate NixOS, Home Manager, and nix-darwin module templates with separated options and config.
cameronraysmithEnforce Nix development conventions for flakes, modules, and platform configurations.
YParesExplain nix module management, troubleshooting, and composition best practices.
