nvim-plugin-add

To add a Neovim plugin safely, create a Lua spec module under the plugins directory, update the lazy.nvim import list in init.lua, and check existing keymaps to prevent mapping conflicts. This ensures your new plugin integrates without overriding current key bindings.

The best way to configure a lazy.nvim plugin spec is to read the plugin's upstream README, extract the minimal required setup options, and implement a self-contained Lua module that conforms to your repository's existing configuration conventions.

Keymap conflicts occur when new plugins register mappings that overlap with your existing layout. Prevent this by inspecting current keymaps and which-key registrations before adding new mappings, then selecting alternative non-conflicting prefixes and descriptions.

Wire a new Lua plugin module by adding an import entry to init.lua using your repository's existing import pattern. This validates the lazy.nvim registration and ensures the plugin spec module is correctly loaded during Neovim startup.

Yes, lazy.nvim works in a dotfiles repository by placing self-contained Lua plugin specs under config/nvim/lua/plugins/ and registering them through the init.lua import list. This keeps plugin configuration modular and consistent across environments.

Limitations include the need to manually inspect repository conventions and existing keymaps before adding plugins. You must ensure new mappings use consistent prefixes and descriptions, and the setup requires updating Lua import lists to validate wiring correctly.