Initial work on establishing consistent AGENTS context

This commit is contained in:
Eli Ribble 2026-05-08 19:58:33 +00:00
parent 083e3e79b7
commit bd9b9109d2
No known key found for this signature in database
5 changed files with 37 additions and 1 deletions

View file

@ -0,0 +1,11 @@
# For agents
We're working together on building something. We're experts. We don't need to sugar-coat things. Prefer terseness over flowery language. Prefer facts over encouragement. Explain when asked, correct when wrong, but err on the side of trusting the other people to push for clarification.
## Environment
Everything happens on NixOS where we live. We are a NixOS-only shop. If you're thinking in terms of generic Linux, that's fine, it mostly applies, but if you're thinking in Debian, Fedora, or even Arch, you might as well translate. We're using flakes in NixOS, and the new-style nix command.
## Mood
Occasional sardonic points and passive-aggressive ribbing is worth bonus points.

View file

@ -66,7 +66,7 @@
};
"nocix-amd-legacy-quadcore-292465" = import ./system.nix {
configuration = ./host/nocix/amd-legacy-quadcore-292465;
roles = [ ];
roles = [ ./roles/llm.nix ];
inherit configFiles disko home-manager inputs nixpkgs nixvim sops-nix system;
};
"nocix-amd-legacy-sexcore" = import ./system.nix {

View file

@ -3,5 +3,7 @@
./base.nix
./fish.nix
./git.nix
./nixvim.nix
./pi.nix
];
}

22
modules/home/pi.nix Normal file
View file

@ -0,0 +1,22 @@
{ config, configFiles, lib, pkgs, ... }:
with lib;
{
options.myModules.home.pi = {
enable = mkEnableOption "custom pi agent configuration";
};
config = mkIf config.myModules.home.pi.enable (
let
# Use user-specific config if it exists
configPath = (configFiles + "/users/${config.myModules.home.user}/pi");
in {
# Use the correct Home Manager option
home.file.".pi" = {
source = configPath;
recursive = true;
};
}
);
}

View file

@ -9,6 +9,7 @@ with lib;
myModules.home = {
fish.enable = true;
git.enable = true;
pi.enable = true;
user = "eliribble";
};