nicolkrit999

Use this skill for general debugging of this nix config whenever it is NOT already known that a build/flake check/rebuild is failing - runtime or boot-time misbehavior, hardware quirks driven by config, config that silently doesn't take effect, code that looks broken but builds, suspected dead/orphaned code, an unresolved issue recorded in a memory file, or any vague observation that something is off. The issue can come from existing code, a memory entry, or a user report alike. Trigger phrases include 'debug this', 'something is wrong with X', 'it builds but doesn't work', 'X stopped working after a successful rebuild', 'this option seems to have no effect', 'is this module even used', 'find dead code', 'look into that unresolved issue from memory', 'retry the fix we reverted', 'debug why X behaves like this'. Drives the frame-investigate-fix-verify loop across nix-debugger, nix-config-architect, nix-package-researcher, nix-checker, and Explore. Does NOT cover a KNOWN-failing build/flake check/rebuild (use d

Use this skill when adding or modifying nix configuration that introduces new functionality, such as new denix modules, enabling programs/services, host constants, theming, or home-manager config. Trigger phrases include 'add a module', 'enable X on host Y', 'install/integrate package Z', 'configure <service> in nix', 'add this to my nixos config', 'set up <program> via home-manager'. Drives the research-author-lint-verify pipeline across nix-package-researcher, nix-config-architect, nix-syntax-linter, and nix-checker. Does NOT cover diagnosing an existing build failure (use debugging-nix-failures instead) or pure attribute/option lookups with no authoring (dispatch nix-package-researcher directly).

Use this skill when new or improved test coverage is needed for a nix module or behavior. Trigger phrases include 'add a test for this module', 'improve test coverage', 'write a test that X', 'register this test', 'test the new module', 'cover this with a test'. Drives the author-run-triage loop across nix-test-author, nix-checker, and nix-debugger. Does NOT cover merely running the existing suite with no new test (dispatch nix-checker directly instead) or authoring non-test config (use creating-nix-modules instead).

Use this skill when a nix change needs cross-platform or cross-architecture judgment before or after authoring. Trigger phrases include 'will this build on the mac', 'is this safe in a shared module', 'where should this module live', 'does this work on aarch64', 'check cross-platform compat', 'is this Linux-only'. Drives the judge-author-verify loop across nix-compat-checker, nix-config-architect, nix-checker, and nix-debugger. Does NOT cover general authoring with no placement/guard question (use creating-nix-modules instead) or diagnosing a failure unrelated to platform differences (use debugging-nix-failures instead).

Use this skill when a nix build, flake check, nixos-rebuild, or darwin-rebuild is failing and needs to be diagnosed and fixed. Trigger phrases include 'the build failed', 'flake check fails', 'nixos-rebuild broke', 'why won't it evaluate', 'fix this nix error', 'option does not exist', 'darwin-rebuild is erroring', 'my rebuild is broken'. Drives the reproduce-diagnose-fix-reverify loop across nix-checker and nix-debugger. Does NOT cover authoring new functionality (use creating-nix-modules instead) or pure style/format sweeps with no build failure (dispatch nix-syntax-linter directly).

Use this skill when creating detailed study notes or course documentation from source material and (optionally) compiling them to PDF - for any CS or math course (linear algebra, calculus, discrete math, statistics, programming). Triggers: 'make notes for this chapter', 'write detailed notes on …', 'turn this course material into a PDF', 'create documentation explaining every topic in …', 'compile these notes to PDF', 'typst/latex notes for …'. Works from ANY course folder (callable by name without an absolute path). Orchestrates reading the source → authoring the explanations → formatting/compiling through the project's `cs-notes` Nix dev environment (Typst, LaTeX via Tectonic, Pandoc, diagrams, plotting, Python). Use whenever study notes / documentation should be produced as a polished file, especially when LaTeX/Typst/PDF compilation is involved. NOT for a page-capped exam cheat sheet (maximal density fitted to a hard page limit) - that's creating-exam-cheat-sheets.

Use this skill when the user wants to bring a brand-new service into this Portainer homelab repo. Trigger phrases include 'add <service> to my homelab', 'set up <service> behind the tunnel', 'create a compose for <service>', 'deploy <service>', 'I want to self-host <service>'. It researches the service, has docker-compose-architect create the new `<service>/docker-compose.yml` per repo rules, runs compose-security-auditor and compose-consistency-linter in parallel, loops fixes back through docker-compose-architect, and hands off the Cloudflare Tunnel target plus the full list of `${VAR}`s to set in Portainer. It does NOT cover auditing or linting services that already exist across the repo (use auditing-compose-repo for that) and it does NOT cover editing an already-deployed service's compose file (dispatch docker-compose-architect directly for that).

Use this skill when the user wants a repo-wide check across services that already exist in this Portainer homelab repo. Trigger phrases include 'audit my composes', 'security check the repo', 'are my composes consistent', 'sweep all services', 'check the whole repo for violations'. It runs compose-security-auditor and compose-consistency-linter across all ~70 service directories in parallel, triages the combined findings by severity with the user, dispatches docker-compose-architect to apply exact fixes, and re-runs only the affected reviewer(s) on the changed services. It does NOT cover onboarding a brand-new service (use adding-compose-services for that, which includes its own scoped review loop) and it does NOT edit files itself - all fixes are applied by docker-compose-architect.

Use this skill when bringing a stack that is currently only running in Portainer under git management in this repo, extracting its live configuration, and templating it per repo conventions. Triggers include 'migrate <stack> to git', 'extract this stack from Portainer', 'bring <service> under git management', 'import the running stack', 'convert my Portainer stack to a template'. Does NOT cover brand-new services that have never been deployed (use adding-compose-services) and does NOT cover repo-wide audits of already-migrated stacks (use auditing-compose-repo).

Use this skill when checking whether the manual copies of the icorsi-notes claude-home agents and skill have drifted from their dotfiles-private source, or re-syncing them after an edit. Triggers include 'sync the icorsi copies', 'check icorsi drift', 'did the icorsi agents drift', 're-sync claude-home', 'I edited the school agents', or any edit to the school cs-material-researcher/cs-notes-auditor/cs-notes-author/cs-notes-formatter agents or the authoring-course-notes skill in ~/dotfiles-private/claude/. Does NOT cover editing the agents or skill content itself (edit in dotfiles-private, then invoke this skill to propagate) and does NOT cover icorsi-notes/claude-home/CLAUDE.md, which is not a copy and is edited in place.

Use this skill when the user says 'add a config for <program>', 'add an alias', 'write a fish function', 'configure my nvim/emacs', 'rice <program>', 'add a utility script', or 'dotfile this' in this PUBLIC dotfiles repo (categorized under general/, linux/, macOS/, various-scripts/, Catppuccin Mocha theme). It routes program-specific work to the right specialist (neovim-configurator, emacs-configurator, shell-config-author, script-author) or to dotfiles-architect for structural/new-program/unclear-placement decisions, verifies with dotfiles-linter (parse checks, secret scan, deployment-mapping check), and ends by handing over the exact ext-dotfiles.nix mapping line(s) needed to actually deploy the new file. Does NOT cover system-level config (NixOS modules, /etc, services - that's the ~/nix repo) and does NOT cover standalone-script requests unrelated to dotfiles.