Stats
Actions
Tags
From sc-skills
Applies Neovim community best practices, plugin architecture patterns, and idiomatic Lua style when writing, reviewing, or refactoring Neovim plugins.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sc-skills:effective-neovimThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Apply best practices from the Neovim community to write clean, idiomatic Lua plugins.
Apply best practices from the Neovim community to write clean, idiomatic Lua plugins.
Use this skill automatically when:
The Type A Neovim developers use:
| Tool | Purpose |
|---|---|
| StyLua | Formatter (opinionated, like prettier) |
| selene | Linter (30+ checks) |
| lua-language-server | Type checking via LuaCATS annotations |
Neovim's own .stylua.toml:
column_width = 100
indent_type = "Spaces"
indent_width = 2
quote_style = "AutoPreferSingle"
From nvim-best-practices (parts upstreamed to :h lua-plugin):
setup(): Plugins should work out of the box. Separate configuration from initialization.<Plug> mappings: Let users define their own keymaps instead of hardcoding bindings.:Rocks install not :RocksInstall, :RocksPrune, etc.require(): Don't load everything at startup. Require inside command implementations.lua/{plugin}/health.lua for :checkhealth.snake_case for functions and variables, PascalCase for classes/modulesplugin-name/
├── lua/
│ └── plugin-name/
│ ├── init.lua # Entry point, setup function
│ ├── health.lua # :checkhealth integration
│ └── *.lua # Module files
├── plugin/
│ └── plugin-name.lua # Auto-loaded, defines commands/autocommands
├── doc/
│ └── plugin-name.txt # Vimdoc for :h plugin-name
└── tests/
└── *_spec.lua # Busted test files
For detailed guidance with code examples, see references/nvim-best-practices.md.
External sources:
:h lua-guide:h lua-pluginnpx claudepluginhub kylesnowschwartz/simpleclaude --plugin sc-skillsValidates, audits, and improves Neovim config (lazy.nvim, GNU Stow). Add plugins, diagnose issues, fix keymaps, and apply best practices.
Guides Prettier plugin ecosystem, custom parsers, and plugin development for JavaScript code formatting. Use for extending or troubleshooting Prettier plugins.
Guides Claude Code plugin creation, directory structure, plugin.json manifest setup, component organization for commands/agents/skills/hooks/lspServers, file conventions, and best practices like auto-discovery and CI integration.