Restructure multi-host Nix configurations into feature-centric modules with flake-parts.
npx skills add https://github.com/mattstruble/skills --skill nix-dendritic
Please help me install this Agent Skill. Skill: nix-dendritic Source: https://github.com/mattstruble/skills/tree/main/nix-dendritic Command: npx skills add https://github.com/mattstruble/skills --skill nix-dendritic
Dendritic standardizes multi-host Nix configurations by applying a feature-centric pattern that structures config around reusable features across NixOS, Darwin, and Home Manager. It is designed for multi-host or cross-platform setups and is not intended for general Nix questions; see the nix skill for those.
Scaffold a new dendritic config using the scaffolding templates and start adding feature modules under modules/.
High-intent search queries and answers about installing and using this skill.
Multi-host Nix configurations can share features across NixOS, Darwin, and Home Manager by applying the Dendritic pattern. This feature-centric approach modularizes capabilities using flake-parts module classes and aspects, composing hosts by importing shared modules rather than aggregating hosts.
The best way to organize a cross-platform Nix flake for scalability is using a feature-centric structure. The Dendritic pattern uses import-tree to auto-load module files, enabling scalable feature sharing without manual imports and discouraging host-centric file organization.
Yes, you can use flake-parts with Home Manager and NixOS modules in a shared configuration. The Dendritic pattern uses flake.modules.<class>.<aspect> to express capabilities, allowing perSystem outputs and layered inheritance patterns across NixOS, Darwin, and Home Manager.
You can auto-load Nix module files without manual imports by using the import-tree tool within the Dendritic pattern. This mechanism automatically loads all module files under the modules/ directory, enabling scalable feature sharing across your multi-host Nix configuration.
You should not use a feature-centric Nix configuration pattern like Dendritic for general Nix questions or single-host setups. It is specifically designed for multi-host or cross-platform environments and standardizes configurations by expressing capabilities as reusable features.
Yes, the Dendritic pattern supports layered system hierarchies for desktop and server hosts. It uses perSystem outputs and inheritance patterns to establish a layered system-default to system-desktop hierarchy across NixOS, Darwin, and Home Manager.
MultipixeloneGuide Nix flake migration to flake-parts for modular multi-system builds.
aytordevGenerate NixOS, Home Manager, and nix-darwin module templates with separated options and config.
JylhisBridge non-flake Nix code with flake tooling using overlay.nix and flake-compat.
benbrastmckieDelegate Nix configuration changes to a dedicated subagent with postflight handling.
