trent-lazyvim_skill
- Shell
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill trentshaines/dotfiles --skill trent-lazyvim- SKILL.md6.2 KB
Overview
This skill helps configure and troubleshoot LazyVim and Neovim for a personal setup. It guides edits to init.lua, plugin files, keymaps, and options, and recommends where to place changes for predictable lazy-loading. Use it to add plugins, customize keybindings, tune LSP/mason, and adapt LazyVim defaults to your workflow.
How this skill works
I inspect the user's Neovim config layout and LazyVim loading order, then suggest concrete edits using lazy.nvim plugin specs or changes in keymaps/options files. I verify where to place changes (lua/plugins/*.lua, lua/config/keymaps.lua, lua/config/options.lua) and provide example snippets and headless commands to list keymaps or validate configuration. I always reference official LazyVim and Neovim docs for syntax and best practices.
When to use it
- Adding or overriding plugins in LazyVim
- Customizing global or plugin-specific keybindings
- Setting editor options, colorscheme, or auto-reload behavior
- Configuring Mason for LSP/DAP/linters
- Debugging plugin load order or lazy-loading issues
- Listing or auditing current keybindings programmatically
Best practices
- Read existing lua/config/*.lua and lua/plugins/*.lua before editing
- Prefer new files in lua/plugins/ for distinct plugin configs to keep diffs small
- Use the plugin 'opts' and 'keys' fields to scope keymaps to plugin activation
- Put core editor settings in lua/config/options.lua and non-essential mappings in keymaps.lua
- Validate Lua syntax and test with :checkhealth and headless Neovim commands
- Reference lazy.nvim and LazyVim docs for supported fields and events
Example use cases
- Add a language plugin via lua/plugins/python-tools.lua using the lazy.nvim spec with opts and keys
- Move a global mapping into lua/config/keymaps.lua to keep it active across buffers
- Force the tokonight colorscheme by setting vim.g.lazyvim_colorscheme in options.lua
- Install and configure Mason servers in lua/plugins/mason.lua so LSPs are auto-managed
- Extract all leader keybindings with the provided headless nvim command to build a cheatsheet
FAQ
Put general mappings in lua/config/keymaps.lua. For plugin-specific mappings, add them in the plugin's keys field so they only load when the plugin is active.
How do I add a new plugin without breaking LazyVim?
Create a new file in lua/plugins/ returning the lazy.nvim spec (author/repo, opts, keys). Follow LazyVim's lazy-loading conventions and test with :Lazy and :checkhealth.
How can I list all leader keybindings programmatically?
Run the headless command that queries vim.api.nvim_get_keymap('n') and filters leader mappings; the skill provides the exact command to run.
