- [Hjem](https://github.com/feel-co/hjem) for home management

- [Hjem](https://github.com/feel-co/hjem) for $HOME management
- No `specialArgs` or janky passing around of configs between layers[^4]
[^4]: Apart from inherit `specialArgs = { inherit inputs; };` for each host. It
    is necessary for any host configuration.

`flake.modules.{nixos,darwin,hjem}`.

`flake.modules.{nixos,darwin}`.

flake.modules.<class>.<feature> = {}

flake.modules.<class>.<aspect> = {}

  flake.modules.hjem.window-manager = { /* ... */ };

> [!NOTE]
> Note that `hjem` modules are automatically included in any host that uses the
> `hjem` module - this may change.

`hjem` modules are included within the `nixos` and `darwin` classes via
`hjem.extraModules` as can be seen below.
I tend to write most configuration inside a `let...in` block and then assign a
single variable to the `<class>.<aspect>` like this:

The `darwin` and `nixos` modules are then used in `modules/hosts.nix`. Modules
are grouped by type at the top of the file to avoid repeated configs and a

```nix
let
  zellijBase =
    {
      pkgs,
      config,
      lib,
      ...
    }:
    let
      inherit (lib.meta) getExe;
      inherit (lib.lists) singleton;
      inherit (config) theme;
    in
    {
      hjem.extraModules = singleton {
        # ... hjem specific config
      };
      # ... rest of config
    }
in
{
  flake.modules.nixos.zellij = zellijBase;
  flake.modules.darwin.zellij = zellijBase;
}
```
The `darwin` and `nixos` classes are then used in `modules/hosts.nix`. Some
aspects are grouped in `modules/aspects.nix` to avoid repeated configs and a

    inherit specialArgs;

    specialArgs = { inherit inputs; };

    inherit specialArgs;

    specialArgs = { inherit inputs; };