dotfiles-nix

How to declaratively add, change, or remove AI coding agent assets — skills, MCP servers, plugin/capability installs, RTK hooks, shared instructions — in this home-manager repo's mods/agents/*.nix module. Use this whenever the user asks to add a skill, add an MCP server, install a plugin for Claude/Codex/OpenCode/Pi, gate something to a specific machine, update a pinned skill, or asks why removing something from mods/agents/*.nix didn't actually remove it after a rebuild. Also use this before writing any new code under mods/agents/ or mods/dotfiles/agents/scripts/, even if the user doesn't name this skill directly — this architecture has specific, non-obvious rules (see "The one rule that matters" and "The three layers") that are easy to violate by copying an old pattern.

Resolve conflicts after Stackman stops during a rebase. Use when stackman sync reports rebase conflicts, when the user asks to continue a Stackman rebase, or when Git is in a conflicted rebase caused by Stackman rebasing a branch onto its parent/upstream branch.

This skill should be used when the user asks about "neovim config", "nvim setup", "vim best practices", "neovim patterns", "modern neovim", "lua configuration", "neovim 0.10", or wants guidance on configuring Neovim following current standards and conventions.

Use when the user wants to handle GitHub pull request feedback, review comments, reviewer suggestions, pasted PR comments, or a PR URL with comments that need triage, code changes, or drafted reviewer replies.

Use when the user explicitly asks to store, create, organize, read from obsidian notes or obsidian vault.

Guide for this Neovim configuration -- a modular Lua-based IDE rooted at mods/dotfiles/nvim/. Use when configuring plugins, adding keybindings, setting up LSP servers, debugging, or extending the config. Covers lazy.nvim, plugin_registry, snacks.nvim pickers, blink.cmp completion, dual LSP architecture, DAP debugging, and which-key v3 aggregation.

Write or update BEHAVIOR.md files that document tool/plugin workflows as portable behavior contracts. Use when the user wants to document keybindings, workflow behaviors, tool conventions, or create per-tool behavior specs for Neovim, tmux, bash, or other keyboard-driven tools. Also use when the user wants to capture "what this tool should do" independently of the current plugin implementation, so that plugins can be swapped without losing workflow preferences.

Implement Neovim plugins and configurations with TDD. Invoke for lua-language implementation tasks.

Karabiner-Elements keyboard configuration using karabiner.ts TypeScript DSL. Use when modifying keyboard layers, shortcuts, modifier swaps, or window management keybindings. Covers simlayers, variable-based layers, and the rift-cli window manager integration.

Nix patterns for flakes, overlays, unfree handling, and binary overlays. Use when working with flake.nix or shell.nix.

Debug Neovim/LazyVim configuration issues. Use when: user reports Neovim errors, keymaps not working, plugins failing, or config problems. Provides systematic diagnosis through hypothesis testing, not just checklists. Think like a detective narrowing down possibilities.