Menu
Configure Neovim with the LazyVim framework in Lua, for plugins, keymaps, options, autocmds, snippets, LSP, formatters, linters, themes. Use when editing files under ~/.config/nvim/lua/.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | neovim-config |
| description | Configure Neovim with the LazyVim framework in Lua, for plugins, keymaps, options, autocmds, snippets, LSP, formatters, linters, themes. Use when editing files under ~/.config/nvim/lua/. |
LazyVim provides the base configuration for Neovim on this system, which is then customized to the user's needs and preferences. This skill works from this point of view, not a vanilla Neovim setup.
~/.config/nvim/ (chezmoi source: private_dot_config/nvim/)~/.config/nvim/snippets/ (chezmoi source: private_dot_config/nvim/snippets/)| File | Purpose |
|---|---|
lua/plugins/*.lua | Plugin specifications (auto-loaded) |
lua/config/keymaps.lua | Custom keybindings |
lua/config/options.lua | Vim options |
lua/config/autocmds.lua | Autocommands |
lazy-lock.json | Plugin version lockfile |
lazyvim.json | LazyVim extras configuration |
Use LazyVim's plugin spec format, not raw lazy.nvim:
-- lua/plugins/example.lua
return {
-- Extend existing plugin
{
"plugin/name",
opts = {
-- Options merge with defaults
},
},
-- Override existing plugin
{
"plugin/name",
opts = function(_, opts)
-- Modify opts table directly
opts.some_option = "value"
end,
},
-- Add new plugin
{
"author/new-plugin",
event = "VeryLazy", -- Lazy-load on event
dependencies = { "nvim-lua/plenary.nvim" },
opts = {},
keys = {
{ "<leader>xx", "<cmd>PluginCommand<cr>", desc = "Description" },
},
},
-- Disable a plugin
{ "plugin/to-disable", enabled = false },
}
-- lua/config/keymaps.lua
local map = vim.keymap.set
-- Format: map(mode, lhs, rhs, opts)
map("n", "<leader>xx", "<cmd>SomeCommand<cr>", { desc = "Description" })
map("v", "<leader>yy", function() ... end, { desc = "Description" })
-- Delete a LazyVim keymap
vim.keymap.del("n", "<leader>existing")
-- lua/config/options.lua
local opt = vim.opt
opt.relativenumber = false
opt.scrolloff = 8
opt.wrap = true
-- lua/config/autocmds.lua
vim.api.nvim_create_autocmd("FileType", {
pattern = { "sql", "python" },
callback = function()
vim.opt_local.tabstop = 4
end,
})
lua/plugins/lang-<name>.lua~/.config/nvim/snippets/<filetype>/<name>.json (chezmoi source: private_dot_config/nvim/snippets/):checkhealth in Neovim:Lazy for plugin errors:verbose map <key> to trace keybindings:messages for startup errorsopts table merging instead of full override when possibledesc for all keymaps (appears in which-key)event, ft, cmd, or keys:Lazy syncLazyVim use LazyDev to configure LuaLS (Lua Language Server) to recognize extra types and Neovim globals like vim. If you see "Undefined global vim" warnings in Neovim plugin config files, this is okay - LazyDev includes these types in the actual editor instance of the LSP server, but does not carry them over to your bash instance of LuaLS.
Browser automation CLI wrapping Playwright for one-shot tasks like navigation, page interaction, screenshots, and scraping. Use when driving a live browser from the terminal. Skip for repeat automations that warrant a full Playwright script.
Author and maintain agent context markdown — AGENTS.md, rules, skills, memory files. Use when creating, editing, or refactoring any agent-focused doc, or after major codebase exploration to capture learning.
Author and audit Agent Skills. Use when creating a new skill, refactoring an existing one, or rewriting skill metadata (name, description, allowed-tools).
Build ASCII/Unicode animations such as loading spinners, logo reveals, particle effects, and terminal art. Covers character grids, frame loops, per-character state machines, ordering, and performance. Use when designing any character-based visual animation.
Run tests, builds, migrations, or any command needing real CI secrets/services on Blacksmith. Use when testing or validating code, or before any commit or push that should be verified against CI.
Use when editing files in a Bun project (bun.lock or bun.lockb at the root, a packageManager field set to bun in package.json, or imports from the bun namespace) or running bun/bunx commands. Covers Bun-native APIs, the bun test runner, bun build --compile, and the Bun-optimized tsconfig.