neovim-pro
Neovim guidance — Lua configuration, lazy.nvim plugin management, LSP setup, Telescope, and Treesitter.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- neovim-pro
- category
- development
- description
- Neovim guidance — Lua configuration, lazy.nvim plugin management, LSP setup, Telescope, and Treesitter.
03 SKILL.md 正文
Overview
Neovim is Vim evolved: the same modal editing, plus a Lua configuration language, built-in LSP client, Treesitter parsing, and a plugin ecosystem (lazy.nvim, Telescope) that makes it a genuine IDE competitor. It's fast, keyboard-driven, and runs anywhere — including over SSH where GUI editors can't follow.
The modern Neovim stack is Lua + lazy.nvim + LSP + Treesitter + Telescope. This skill covers configuring that stack well: startup performance, LSP for your languages, fuzzy finding, and the options that make daily editing pleasant.
When to use
- Setting up Neovim from scratch or migrating from Vim/VS Code.
- Configuring LSP for a language (completions, go-to-definition, diagnostics).
- Debugging slow startup or plugin issues.
- Choosing plugins (or deciding you need fewer).
- Writing Lua config and custom keymaps.
- Using Telescope, Treesitter, and modern editing plugins.
Core concepts
- Lua config.
init.luareplacing vimscript —vim.opt,vim.keymap.set,vim.api. Lua is faster and more expressive; keep config organized (lua/config/options.lua,keymaps.lua,plugins/). - lazy.nvim. The plugin manager: lazy-loading by event/cmd/ft/keys, lockfile (
lazy-lock.json) for reproducible installs, profiling (:Lazy profile) for startup analysis. Lazy-load everything that isn't needed at startup. - LSP (built-in client). Language servers via
nvim-lspconfig(orvim.lsp.configin 0.11+): completions, hover, go-to-definition, references, rename, diagnostics, code actions. Mason installs servers; configure per-language settings deliberately. - Treesitter. Real parsing (not regex) for highlighting, indentation, text objects, and incremental selection. Install parsers for your languages;
:TSUpdatekeeps them current. This is what makes highlighting correct. - Telescope. Fuzzy finder for files, grep, buffers, LSP symbols, git — the command palette of Neovim. Configure
live_grepwith ripgrep args; learn the core pickers deeply rather than installing ten finders. - Completion. nvim-cmp (or blink.cmp) wired to LSP + snippets + buffer/path sources. Snippets (LuaSnip) for boilerplate. Tune: completion should feel instant, not a popup lottery.
- Formatting/linting. conform.nvim / nvim-lint bridging external tools (prettier, ruff, stylua) — format-on-save with fallback to LSP formatting. Keep formatting deterministic across the team (same configs as CI).
- Keymaps.
<leader>(space) as the namespace; consistent mnemonics (<leader>fffind files,<leader>fggrep,<leader>cacode action). Document your maps (:map, which-key) — undiscoverable maps don't exist. - Options that matter.
number/relativenumber,expandtab/shiftwidthper language,undofile(persistent undo — non-negotiable),ignorecase/smartcase,scrolloff,signcolumn=yes(no layout shift),updatetime(CursorHold responsiveness). - Diagnostics. Virtual text vs signs vs float — configure for readability;
[d/]dnavigate;<leader>efloat for details. Diagnostics should inform, not decorate. - Sessions/projects. Session management (persistence.nvim, or built-in
:mksession) per project; project-root detection. Restore your layout where you left it. - Startup profiling.
--startuptime,:Lazy profile— measure plugin cost; the usual suspects are colorschemes doing too much and plugins loading eagerly that should be lazy. - Terminal integration.
:terminalbuffers, toggleterm for floating terminals — Neovim as the whole workspace, not just the editor pane. - Remote editing. Neovim over SSH (it's a terminal app) — the killer feature vs GUI editors for server work.
Practical workflow
- Structure the config.
init.luabootstrapping lazy.nvim, then modules:-- init.lua require("config.options") require("config.keymaps") require("config.lazy") -- bootstraps lazy.nvim, imports plugins/ - Set options first. The sane baseline before any plugins:
vim.opt.number = true; vim.opt.relativenumber = true vim.opt.expandtab = true; vim.opt.shiftwidth = 2; vim.opt.tabstop = 2 vim.opt.undofile = true; vim.opt.ignorecase = true; vim.opt.smartcase = true vim.opt.signcolumn = "yes"; vim.opt.updatetime = 250 vim.g.mapleader = " " - Install lazy.nvim with lazy-loading. Specs with
event,cmd,ft,keys— nothing loads before it's needed:{ "nvim-telescope/telescope.nvim", cmd = "Telescope", keys = { { "<leader>ff", "<cmd>Telescope find_files<cr>" } }, dependencies = { "nvim-lua/plenary.nvim" } } - Configure LSP per language. Mason for installation, lspconfig for setup, on_attach keymaps (gd, gr, K, <leader>ca, <leader>rn):
vim.api.nvim_create_autocmd("LspAttach", { callback = function(args) local map = function(m, lhs, rhs) vim.keymap.set(m, lhs, rhs, { buffer = args.buf }) end map("n", "gd", vim.lsp.buf.definition) map("n", "gr", vim.lsp.buf.references) map("n", "K", vim.lsp.buf.hover) map("n", "<leader>rn", vim.lsp.buf.rename) map("n", "<leader>ca", vim.lsp.buf.code_action) end, }) - Add Treesitter. Ensure installed parsers for your languages; enable highlight/indent; add text objects (
@function.outer) — editing by syntax nodes. - Wire completion + formatting. cmp/blink with LSP source; conform.nvim format-on-save matching CI's formatter config.
- Profile startup.
:Lazy profile,--startuptime; lazy-load offenders; target sub-100ms. - Version everything. Config in git;
lazy-lock.jsoncommitted; new machine setup is clone + open.
Common pitfalls
- Eager-loading everything — 800ms startup; lazy-load by event/cmd/ft.
- No lockfile committed — plugin updates breaking config; commit
lazy-lock.json. - LSP configured but Mason missing servers — "LSP not working"; ensure servers installed and attached (
:LspInfo). - Conflicting formatters — LSP format + conform fighting; pick one path per language.
- Vimscript in Lua config — mixing styles; commit to Lua (
vim.opt, notset). - Undiscoverable keymaps — maps nobody remembers; which-key + documented leader mnemonics.
- No persistent undo — losing undo history on close;
undofileis one line. - Signcolumn layout shift — diagnostics jumping text;
signcolumn=yesalways. - Treesitter parsers missing — broken highlighting;
:TSUpdateand ensure_installed. - Plugin hoarding — 60 plugins, 10 used; audit quarterly, remove ruthlessly.
- Colorscheme without terminal true-color — wrong colors; fix terminal/tmux first.
- Ignoring
:checkhealth— built-in diagnostics for providers, parsers, LSP; run it first when debugging. - Leader key conflicts — plugins stealing your leader maps; check with
:verbose map.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).