메뉴
Neovim Lua configuration and plugin development guidance. Use when editing Neovim config, lazy.nvim plugin specs, Lua modules under nvim/, keymaps, autocmds, highlights, LSP setup, diagnostics, Treesitter integration, colorschemes, or Neovim plugin code.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | neovim-lua |
| description | Neovim Lua configuration and plugin development guidance. Use when editing Neovim config, lazy.nvim plugin specs, Lua modules under nvim/, keymaps, autocmds, highlights, LSP setup, diagnostics, Treesitter integration, colorschemes, or Neovim plugin code. |
Use this skill for Neovim configuration and plugin work. Prefer idiomatic Lua, stable Neovim APIs, and the repo's existing lazy.nvim organization.
nvim/ structure and relevant lazy.nvim specs before editing.vim.api, vim.keymap.set, vim.opt, vim.lsp, and vim.diagnostic over stringly vim.cmd when direct APIs exist.event, ft, cmd, or keys triggers.references/nvim-api.md for buffers, windows, namespaces, autocmds, keymaps, highlights, and common vim.api calls.references/nvim-lsp.md for vim.lsp setup, handlers, capabilities, and client behavior.references/nvim-diagnostics.md for vim.diagnostic signs, virtual text, float behavior, and config.references/nvim-treesitter.md for Treesitter parsers, nodes, queries, and syntax-aware work.Use when asked to find first customers, early adopters, design partners, beta users, or leads for a startup or product idea, to research who might buy, to define an ideal customer profile (ICP), or to validate early demand from public signals — given a product URL, repository, or description.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Feedback-loop-first diagnosis for hard bugs and performance regressions — build a tight red-capable repro loop before hypothesising.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Compact the current conversation into a handoff document for another agent to pick up.
Feedback-loop-first diagnosis for hard bugs and performance regressions — build a tight red-capable repro loop before hypothesising.