Create lazy.nvim plugin specs with triggers and keymaps in lua/plugins.
npx skills add https://github.com/ThorstenRhau/neovim --skill add-plugin-thorstenrhau
Please help me install this Agent Skill. Skill: add-plugin Source: https://github.com/ThorstenRhau/neovim/tree/main/.claude/skills/add-plugin Command: npx skills add https://github.com/ThorstenRhau/neovim --skill add-plugin-thorstenrhau
This Skill provides a structured approach to adding a new lazy.nvim plugin spec that adheres to the project's conventions, ensuring consistency and reducing setup mistakes.
Create a new lazy.nvim plugin spec placed in lua/plugins/<category>.lua following the project conventions.
High-intent search queries and answers about installing and using this skill.
To standardize lazy.nvim plugin specs, you enforce declarative opts, explicit lazy-load triggers, and documented keymaps. This ensures consistent file placement and valid Lua specs aligned with project conventions for immediate config use.
Lazy.nvim plugin specifications should be placed under lua/plugins/<category>.lua files. Categorizing specs by purpose—such as editor, git, lsp, ui, picker, or treesitter—enforces repository style guidelines and maintains consistent configuration organization.
The best way to configure lazy-load triggers is by defining explicit event, cmd, or keys attributes in the spec. This declarative approach ensures plugins load only when needed, reducing startup time and maintaining valid Lua configuration.
Yes, you can automatically incorporate UI borders and leader-key prefixes to align with existing config conventions. The specification process mandates properly documented keymaps with descriptive categories to ensure consistent user interface behavior.
No, adding a lazy.nvim plugin automates creation and placement to enforce project conventions. It categorizes specs by purpose under lua/plugins/ and produces a valid Lua spec with proper triggers, eliminating manual path configuration errors.
Declarative opts are required to enforce project conventions and reduce setup mistakes. By mandating explicit lazy-load triggers and properly documented keymaps, the specification process ensures consistent file placement and valid Lua configuration across the repository.
barnabasJConfigure modular Neovim setups with lazy.nvim, LSP, and Treesitter.
AbsolutelySkilledAutomate Neovim configuration and plugin management with Lua workflows.
NeKon69Provide API reference and commands for the nvim-treesitter-context Neovim plugin.
geoffjayAutomate add, update, remove, and validate operations on marketplace.json plugin catalogs.
