agentleFS
iulianditaiuliandita/skills/skills/nixos/SKILL.md

nixos

Skill12 starsChanged yesterdayMITView on GitHub

NixOS and Nix: configuration.nix, flakes, nixos-rebuild, Home Manager, nix-darwin, overlays, dev shells, sops-nix. Use for failing rebuilds, rollbacks.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 10 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before returning NixOS or Nix commands, verify:

    line 81
  2. Distinctive:

    Start narrow. Widen only when the failing layer is still unclear.

    line 131
  3. Distinctive:

    Add subsystem probes only when the task needs them:

    line 169
  4. Distinctive:

    Do not load every reference by default.

    line 205
  5. Very specific:

    Run nixos-rebuild dry-activate --flake .#host before switch when the risk is nonzero.

    line 220
  6. Very specific:

    Prefer test over switch when the change might break login.

    line 221
  7. Very specific:

    Avoid touching system.stateVersion.

    line 224
  8. Very specific:

    Keep overlays composable: scope to final: prev: { ...

    line 225
  9. Distinctive:

    If a check fails, fix the layer it points to and return to Step 4.

    line 252
  10. Distinctive:

    Keep triage cross-layer and boring:

    line 259
  11. Distinctive:

    Prefer rollback to reinstall.

    line 265
  12. Very specific:

    When a problem looks "flake-only," default to rolling the suspect input back to its previous rev with nix flake lock --override-input.

    line 285
  13. Distinctive:

    Flakes when the user already has them: Do not migrate users off channels mid-troubleshoot.

    line 295
  14. Distinctive:

    Generations are the rollback: Before debugging, confirm the previous generation boots.

    line 296
  15. Distinctive:

    Secrets never go in the store: Use sops-nix or agenix with activation-time decryption.

    line 303
  16. Very specific:

    Secrets never in the store: Use sops-nix or agenix with activation-time decryption.

    line 364

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

NixOS, Nix, and Flakes Administration

Administer NixOS without falling back into imperative distro muscle memory. NixOS is declarative, functional, and atomic: the system is a value computed from a configuration, every change becomes a new immutable generation in /nix/store, and rollbacks are a bootloader entry away.

This skill keeps that model intact, then layers in the practical stack: channels vs flakes, nixos-rebuild vs nix CLI, home-manager, nix-darwin, store hygiene, overlays, module writing, secrets, and the Determinate Nix and Lix lanes.

The places NixOS breaks are NixOS-shaped: channel drift, flake input staleness, garbage collection that nukes a needed derivation, overlays fighting, nix-env -i poisoning the user profile, hardware modules missing, or people treating /etc/nixos/configuration.nix like a normal Linux config file.

Why people run it. Atomic upgrades and rollbacks, bit-for-bit reproducible systems, disposable dev shells, fleet-wide configuration without a separate config-management tool, and a single language for a workstation, a server, a container image, a NixOS VM, and a macOS laptop via nix-darwin.

Target versions: see references/versions.md (verified per the receipt date in that file). Do not restate version numbers here.

When to use

  • NixOS system administration: configuration.nix, modules, options, imports, and /etc/nixos workflow
  • Flake work: flake.nix, flake.lock, inputs, outputs, nix flake update, nix flake check
  • nixos-rebuild flow: switch, test, boot, dry-activate, build-vm, and rollback
  • Channels, pinning, and input management: nix-channel, nix registry, npins, niv, flake inputs
  • home-manager (standalone, NixOS module, or nix-darwin module) for user-level declarative config
  • nix-darwin on macOS: declarative system config, Homebrew integration, LaunchDaemons
  • Nix store and derivations: nix-store, nix store, GC roots, nix-collect-garbage, optimise-store
  • Dev environments: nix-shell, nix develop, shell.nix, default.nix, direnv with nix-direnv
  • Overlays, overrides, and package customisation: overlays, overrideAttrs, override, pin patches
  • Writing NixOS modules: options, config, assertions, conditionals, imports, mkMerge, mkForce
  • Secrets management: sops-nix, agenix, nix-sops, ragenix, activation-time decryption
  • Declarative disks and filesystems: disko, btrfs layouts, LUKS, ZFS, impermanence patterns
  • Remote installs and imaging: nixos-anywhere, nixos-install, nixos-generate, SD images, ISO images
  • Hardware enablement: nixos-hardware profiles, firmware, kernel choice, GPU drivers
  • Unfree and insecure packages: allowUnfree, permittedInsecurePackages, NIXPKGS_ALLOW_*
  • Boot and generations: systemd-boot vs GRUB, kernel selection, nix-env --list-generations, boot entries
  • Garbage collection strategy: retention, GC roots, nix.gc.automatic, auto-optimise-store
  • Determinate Nix lane: Determinate installer, flakes-on-by-default, enterprise backports
  • Lix lane: fork-specific behavior, coexistence, and migration notes
  • Integration with Docker, Kubernetes, and CI: nix build, image outputs, cachix, attic

When NOT to use

  • Arch or CachyOS administration - use arch-linux
  • Debian, Ubuntu, Mint, or Pop!_OS administration - use debian-ubuntu
  • Fedora, RHEL, CentOS Stream, Rocky, or Alma administration - use rhel-fedora
  • Kali Linux and offensive-tool distros - use debian-ubuntu
  • Shell syntax, quoting, or portability outside Nix expressions - use shell-scripting
  • Docker, Podman, image builds, or container runtime issues - use docker
  • Kubernetes cluster or manifest work - use kubernetes
  • Fleet-wide non-Nix Linux configuration via playbooks - use ansible
  • Terraform or OpenTofu infrastructure code - use terraform
  • CI/CD pipeline design for Nix-based builds (cachix push, build farm, pipeline stages) - use ci-cd
  • Offensive or privesc testing - use privilege-escalation (opt-in; if installed)
  • Repository-wide vulnerability audits of Nix code - use security-audit; NixOS host hardening stays in this skill
  • OPNsense or pfSense appliance work - use opnsense-pfsense

AI Self-Check

Before returning NixOS or Nix commands, verify:

  • Lane identified: NixOS install, Nix on non-NixOS Linux, Nix on macOS (nix-darwin or plain Nix), WSL, Determinate Nix, or Lix. Advice diverges fast.
  • Channels vs flakes decided: confirm which the user has (and stable vs unstable, home-manager, or nix-darwin context) before prescribing nix-channel, nixos-rebuild --flake, or nix flake update. Mixing without intent creates channel-lock drift.
  • Flake status is current: flakes remain nominally experimental on upstream Nix but are enabled by default on Determinate Nix; recommend enabling experimental-features = nix-command flakes where the user is already using flakes.
  • nix-env -i is not the answer: installing into the per-user profile hides state from configuration.nix and breaks reproducibility. Use declarative environment.systemPackages, home.packages, or an ad-hoc nix shell instead.
  • No partial upgrade advice: on flakes-based systems, do not bump a single input without running nixos-rebuild --flake after; on channels, do not change only nixos without updating dependent channels too.
  • Rebuild verb is intentional: switch, test, boot, dry-activate, build-vm, and build differ. test does not persist the boot entry; boot does not activate now; switch does both.
  • Known-good generation preserved: identify the rollback generation, boot entries, and store or cache state before changes. Never remove the last known-good generation, and never nix-collect-garbage -d on a system that just booted a new generation; boot the new generation twice before pruning.
  • GC roots respected: dev shells, direnv caches, and CI artifacts often hold GC roots. Do not recommend aggressive GC without checking nix-store --gc --print-roots first.
  • Unfree / insecure gates named explicitly: set nixpkgs.config.allowUnfree = true; or allowUnfreePredicate, and list insecure packages under permittedInsecurePackages. Do not default to NIXPKGS_ALLOW_UNFREE=1 as the permanent answer.
  • Hardware module present: for fresh installs, hardware-configuration.nix must be regenerated with nixos-generate-config and not hand-edited for filesystem UUIDs. For laptops, check nixos-hardware profile.
  • Kernel and initrd coherence: boot.kernelPackages, initrd modules, filesystems, and bootloader agree. Do not casually swap kernels on a system with ZFS, NVIDIA, or custom out-of-tree modules.
  • Module fields real: options named in advice exist in the version of nixpkgs the user has. options graveyards drift between NixOS releases - verify against the nixpkgs tag the user pinned.
  • Secrets not put in the store: anything under ./secret.age, ./sops.yaml, or similar must be decrypted at activation time by sops-nix or agenix, not embedded directly in a Nix string that ends up world-readable in /nix/store.
  • disko / impermanence claims match the install: declarative disk layouts change the recovery story. Confirm partition, filesystem, and subvolume layout before prescribing rollback or wipe steps.
  • home-manager mode identified: standalone, NixOS module, or nix-darwin module. home-manager switch vs nixos-rebuild switch vs darwin-rebuild switch is not interchangeable.
  • Overlay placement sane: overlays belong in nixpkgs.overlays (NixOS) or as a flake input overlay. Do not recommend global ~/.config/nixpkgs/overlays.nix on a flakes system where that path is often ignored.
  • Determinate / Lix advice scoped: Determinate's determinate-nixd (run via nix-daemon.service on Linux) and Lix's CLI diverge from upstream in subtle places. Name the lane before suggesting daemon or CLI flags.
  • Diagnostic errors are not silenced: do not hide useful output with 2>/dev/null when the error text is the evidence. Use 2>&1 || true when gathering.
  • Version pins justified: if a pinned system.stateVersion is suggested, explain why; do not change stateVersion on an existing system casually - it controls migration semantics.
  • Cross-cutting agent hygiene applied - see references/agent-hygiene.md

Workflow

The steps are ordered. Copy this checklist and track progress:

  • Step 1: Nix lane identified
  • Step 2: Current state gathered
  • Step 3: Matching reference loaded
  • Step 4: One layer changed; consequential changes confirmed first
  • Step 5: Validated (on failure, fix and return to Step 4)

Step 1: Identify the Nix lane first

LaneDefault stanceWhat changes
NixOS installed (stable release)configuration.nix or flake.nix drives everythingfull system is Nix-managed; rollbacks via bootloader
NixOS unstable / next pre-releasetreat as rolling-ishexpect breakage; verify options still exist
Nix on non-NixOS Linuxuser-level onlyhost distro still owns services and boot; no nixos-rebuild
nix-darwin on macOSdeclarative macOS configdarwin-rebuild switch; host owns kernel and firmware
Plain Nix on macOS (no darwin)package manager onlynix profile or nix shell for user tooling
WSL2 with NixOSfull NixOS in WSLboot and init differ; host owns kernel
Determinate Nixflakes on by default, daemon binary differs (Linux unit stays nix-daemon.service)determinate-nixd, parallel eval, lazy trees
Lixupstream-compatible forkCLI mostly matches; internals, error messages, and Meson build diverge

Step 2: Gather current system state

Start narrow. Widen only when the failing layer is still unclear.

Baseline checks for every NixOS or Nix case:

# Identify OS and Nix lane
cat /etc/os-release 2>&1 || true
nix --version
command -v nixos-version >/dev/null 2>&1 && nixos-version
command -v darwin-version >/dev/null 2>&1 && darwin-version
command -v determinate-nixd >/dev/null 2>&1 && determinate-nixd status
uname -a

# Nix config and features
nix config show 2>&1 | grep -E 'experimental-features|extra-experimental|substituters|trusted-users' || true
cat /etc/nix/nix.conf 2>&1 || true

# NixOS-specific
[[ -d /etc/nixos ]] && ls /etc/nixos
[[ -f /etc/nixos/flake.nix ]] && echo "flakes system" || echo "channels system (or flake elsewhere)"
command -v nix-channel >/dev/null 2>&1 && nix-channel --list 2>&1 || true
command -v nixos-rebuild >/dev/null 2>&1 && nixos-rebuild --help 2>&1 | head -5

# Generations and boot
command -v nix-env >/dev/null 2>&1 && nix-env --list-generations -p /nix/var/nix/profiles/system 2>&1 | tail -5 || true
[[ -d /boot/loader/entries ]] && ls /boot/loader/entries 2>&1 | tail -10
command -v bootctl >/dev/null 2>&1 && bootctl status 2>&1 | head -20 || true

# Store health and GC state
df -h /nix/store
du -sh /nix/store 2>&1 || true
if gc_roots=$(nix-store --gc --print-roots); then
  printf '%s\n' "$gc_roots" | sed '/^$/d' | wc -l
else
  printf '%s\n' 'GC root inspection failed; count is unknown.' >&2
fi

Add subsystem probes only when the task needs them:

# home-manager
command -v home-manager >/dev/null 2>&1 && home-manager generations | head -5

# flake state
[[ -f flake.nix ]] && nix flake metadata 2>&1 | head -20
[[ -f flake.lock ]] && nix flake check --no-build 2>&1 || true

# services and logs (NixOS)
systemctl --failed 2>&1 || true
journalctl -b -p warning..alert 2>&1 | tail -30 || true

# hardware (NixOS)
lspci -k 2>&1 | grep -Ei 'vga|3d|display|network' || true
journalctl -b 2>&1 | grep -Ei 'nvrm|nvidia|amdgpu|i915|xe|drm|firmware' || true

Step 3: Load only the relevant reference

Task typeReference
configuration.nix, modules, options, assertions, mkForce/mkMergereferences/configuration-and-modules.md
flakes, inputs, lockfile, nix flake, registry, input followsreferences/flakes-and-channels.md
nixos-rebuild verbs, generations, rollback, boot entries, dry-activatereferences/rebuild-generations-and-rollback.md
home-manager (standalone, NixOS module, nix-darwin module)references/home-manager-and-darwin.md
overlays, overrideAttrs, override, packaging, mkDerivation, patchingreferences/overlays-packaging-and-overrides.md
Nix store, nix-store, GC roots, nix-collect-garbage, optimise-store, CASreferences/store-gc-and-builders.md
dev shells, nix develop, shell.nix, direnv with nix-direnvreferences/dev-shells-and-direnv.md
disko, impermanence, nixos-anywhere, SD/ISO images, nixos-generatorsreferences/disko-impermanence-and-imaging.md
hardware, firmware, kernels, nixos-hardware, GPU drivers, Wayland desktopreferences/hardware-desktop-and-kernel.md
secrets: sops-nix, agenix, activation decryption, keyringsreferences/secrets-sops-and-agenix.md
Determinate Nix, Lix, lane-specific behavior, migration notesreferences/determinate-lix-and-lanes.md
recurring NixOS and Nix footguns, edge cases, upgrade breakagereferences/gotchas-and-special-situations.md

Do not load every reference by default. Pick the one that matches the failure mode.

Step 3.5: Stay here or hand off

Request shapeRoute
NixOS install, module, flake, rebuild, rollback, store, overlay, disko, secretsstay in nixos
Build a Docker or OCI image from Nix (dockerTools, nix2container)stay here for the Nix build, hand to docker for runtime
Deploy a NixOS box into K8s (nixos-in-kube, custom images)start here, hand to kubernetes for the cluster side
Review Nix-produced container for OWASP / supply chain issuesstay for the Nix build; use security-audit for the audit
Write a bash one-liner or zsh function that wraps nix callsuse shell-scripting

Step 4: Change one layer at a time

  • Fix flake or channel state before blaming nixos-rebuild.
  • Run nixos-rebuild dry-activate --flake .#host before switch when the risk is nonzero.
  • Prefer test over switch when the change might break login; test does not persist the boot entry, so a reboot returns to a known-good generation.
  • Fix option-name drift before blaming module logic: nix repl -f '<nixpkgs/nixos>' -I ... and :p config.services.foo beat guessing.
  • On home-manager, run home-manager switch separately if it is standalone; otherwise nixos-rebuild switch picks it up when it is wired as a module.
  • Avoid touching system.stateVersion. It anchors migration semantics.
  • Keep overlays composable: scope to final: prev: { ... }, not mutating pkgs in-place.
  • Validate before GC: nix-store --gc --print-roots | grep <path> before deleting.

Consequential changes (generation deletion and GC, kernel or bootloader changes, disko --mode destroy, image writes with dd, nixos-anywhere installs, secret re-keying): show the exact command and what it will do (generations kept, dry-activate output, or target device), get explicit confirmation, run it, then go to Step 5. In unattended runs, stop at the plan. Exact commands live in references/rebuild-generations-and-rollback.md (rollback, generation pruning), references/store-gc-and-builders.md (GC), references/disko-impermanence-and-imaging.md (disks, images, remote installs), and references/secrets-sops-and-agenix.md (re-keying).

Step 5: Validate before closing

# System state
nixos-version 2>&1 || true
nix-env --list-generations -p /nix/var/nix/profiles/system | tail -5
systemctl --failed 2>&1 || true

# Flake sanity
[[ -f flake.nix ]] && nix flake check --no-build

# Store sanity
nix-store --verify --check-contents 2>&1 | tail -20
df -h /nix/store

If a check fails, fix the layer it points to and return to Step 4. Reboot only when the boot path is understood and at least one known-good generation remains.


Troubleshooting Pattern

Keep triage cross-layer and boring:

  1. Confirm the Nix lane (NixOS vs Nix-on-host, flakes vs channels, Determinate vs upstream vs Lix).
  2. Identify the failing layer: input state, evaluation, build, activation, or runtime service.
  3. Pull the right logs before changing config.
  4. Change one layer at a time and retest.
  5. Prefer rollback to reinstall. Generations are the whole point.

Core log sweep on NixOS:

journalctl -b -p warning..alert
journalctl --user -b
dmesg --level=err,warn
journalctl -u nix-daemon -b
journalctl -u nixos-rebuild -b 2>&1 || true

Build and eval failures are loudest in the rebuild output itself; pipe through --show-trace and, for opaque errors, --print-build-logs. Capture them with build, which evaluates and builds without activating anything or changing the boot entry:

nixos-rebuild build --flake .#host --show-trace --print-build-logs 2>&1 | tail -200

When a problem looks "flake-only," default to rolling the suspect input back to its previous rev with nix flake lock --override-input. To isolate hardware from config, build the same output on another machine with the same flake.lock. Re-lock from scratch only as a last resort, after committing the current flake.lock.


Default Decisions

  • Declarative first. nix-env -i, nix profile install, and one-off nixpkgs.config tweaks are escape hatches, not workflows. If it survives across rebuilds, it belongs in the config.
  • Flakes when the user already has them. Do not migrate users off channels mid-troubleshoot. Do not migrate users onto flakes without naming tradeoffs (still experimental upstream, lockfile commits become a habit, registry overrides differ).
  • Generations are the rollback. Before debugging, confirm the previous generation boots. That is cheaper than chasing ghosts.
  • Store hygiene is boring and scheduled. Enable nix.gc.automatic and nix.settings.auto-optimise-store = true; rather than manual sweeps.
  • Build narrow, cache deliberately. Evaluate and build targeted attributes before rebuilding entire systems where possible; use binary caches and substituters deliberately, since local source builds can dominate iteration time.
  • Keep the config reviewable. Separate hardware, secrets, user packages, and service modules enough to review changes safely. Commit flake.nix and flake.lock before a flake rebuild, and keep input bumps in their own commit.
  • home-manager has three modes. Standalone, NixOS module, nix-darwin module. Pick one per host and stay there.
  • nix-darwin is opinionated. macOS system settings, LaunchDaemons, and Homebrew coexistence are what it owns. Do not treat it like NixOS with a different kernel.
  • Disko and impermanence are declarative recovery. They shine on fresh installs and nixos-anywhere deploys; retrofitting them onto a live system is a different, harder problem.
  • Secrets never go in the store. Use sops-nix or agenix with activation-time decryption.
  • Pick Determinate or Lix intentionally. Both are fine; both add behavior that diverges from upstream Nix in small but real ways. Name the lane.
  • Kernel changes are cross-layer. ZFS, NVIDIA, hardened kernel, and custom initrd modules all interact. Do not swap boot.kernelPackages casually.

Quick Triage Checklist

Match the symptom to its first checks with the table in references/quick-triage.md.


Reference Files

  • references/configuration-and-modules.md - /etc/nixos/configuration.nix, modules, options, assertions, mkMerge and mkForce, NixOS module system
  • references/flakes-and-channels.md - flakes, flake.nix anatomy, inputs and outputs, flake.lock, nix flake verbs, channels vs flakes vs npins
  • references/rebuild-generations-and-rollback.md - nixos-rebuild verbs, generations, nix-env --list-generations, bootloader entries, rollback flow
  • references/home-manager-and-darwin.md - home-manager (standalone, NixOS module, nix-darwin module), nix-darwin system configuration on macOS
  • references/overlays-packaging-and-overrides.md - overlays, overrideAttrs, override, callPackage, writing derivations, patching upstream
  • references/store-gc-and-builders.md - Nix store, nix-store vs nix store, GC roots, nix-collect-garbage, optimise-store, remote builders, Cachix and attic
  • references/dev-shells-and-direnv.md - nix-shell, nix develop, shell.nix, default.nix, flake dev shells, nix-direnv, per-project env
  • references/disko-impermanence-and-imaging.md - disko partitioning, impermanence, nixos-anywhere, SD/ISO images with nixos-generators
  • references/hardware-desktop-and-kernel.md - nixos-hardware, kernel selection, firmware, GPU drivers, Wayland and X11, display managers
  • references/secrets-sops-and-agenix.md - sops-nix, agenix, activation-time decryption, age key management, avoiding store-world-readable secrets
  • references/determinate-lix-and-lanes.md - Determinate Nix (enterprise lane, daemon differences, flakes-on-by-default), Lix (compat-focused fork), coexistence
  • references/gotchas-and-special-situations.md - recurring NixOS and Nix failure patterns and edge cases
  • references/quick-triage.md - symptom to first-checks triage table

Output Contract

See references/output-contract.md for the full contract.

  • Skill name: NIXOS
  • Deliverable bucket: audits
  • Mode: conditional. When invoked to analyze, review, audit, or improve existing repo content, apply the reporting size and evidence rules in references/output-contract.md and write the deliverable to docs/local/audits/nixos/<YYYY-MM-DD>-<slug>.md. When invoked to answer a question, teach a concept, build a new artifact, or generate content, respond freely without the contract.
  • Severity scale: P0 | P1 | P2 | P3 | info (see shared contract; only used in audit/review mode).

Related Skills

  • arch-linux - Arch and CachyOS administration. Use it when the host is Arch-family and Nix is a side tool, not the system.
  • debian-ubuntu - Debian-family administration. Use it when Nix runs on Debian/Ubuntu as a user-level package manager only.
  • rhel-fedora - RHEL-family administration. Use it when Nix runs on Fedora/RHEL as a user-level package manager only.
  • debian-ubuntu - Kali distro workflow. Use it for Kali, not for Nix inside Kali.
  • shell-scripting - shell syntax, aliases, and one-liners outside Nix expressions.
  • docker - container runtime and image concerns. This skill builds images with dockerTools; docker runs them.
  • kubernetes - cluster workloads once the build output leaves Nix.
  • ansible - fleet config management when Nix is not the chosen tool for the job.
  • terraform - IaC for cloud resources that host NixOS VMs; this skill owns the guest.
  • security-audit - defensive review of a Nix-built artifact.
  • ci-cd - pipeline design when the CI side of a Nix build (cachix push, remote builders, pipeline stages) is the primary concern.
  • privilege-escalation (opt-in; if installed) - offensive and privesc testing; this skill covers NixOS administration, not exploitation.
  • opnsense-pfsense - OPNsense/pfSense appliance work; this skill covers NixOS-based hosts, not BSD appliances.
  • update-docs - sync docs after substantial module or flake restructuring.

Rules

  1. Confirm consequential changes before running them. Show the exact command and its plan, wait for an explicit yes, then verify. Unattended runs stop at the plan.
  2. Secrets never in the store. Use sops-nix or agenix with activation-time decryption; anything else ends up world-readable in /nix/store.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.