neovimcraft.com

On neovimcraft, a pre-made configuration is a complete Neovim setup you can adopt as your starting point, while a plugin is a single add-on that extends one specific part of Neovim. The site lists both in the same curated directory, but they sit under different categories: pre-made-configuration for full setups and functional tags like colorscheme, lsp, or fuzzy-finder for individual plugins. If you want a working editor quickly, start with a configuration. If you want to add one capability to an existing setup, start with a plugin.

How the two categories differ

The directory shows pre-made-configuration with 35 entries, so it is a small slice of the 1,368 results — most of what neovimcraft indexes is individual plugins.

What a pre-made configuration actually contains

A configuration is not a plugin with extra features; it is a bundle. nvim-lua/kickstart.nvim is described as "a launch point for your personal nvim configuration," meaning it is meant to be forked and edited rather than used untouched. siduck76/NvChad is described as a "Neovim framework providing solid defaults and a beautiful UI," and LazyVim/LazyVim is a full distribution built on top of the plugin manager folke/lazy.nvim.

The practical consequence: adopting a configuration usually means you also adopt its plugin manager, its keybinding conventions, and its defaults. Those defaults are the point — they save you from assembling dozens of plugins yourself — but they also mean changing one behavior can require understanding how the whole config is wired.

What a plugin actually contains

A plugin does one job. folke/lazy.nvim is a plugin manager; nvim-telescope/telescope.nvim is a fuzzy finder. Neither assumes anything about the rest of your setup beyond Neovim itself. You install it, configure it, and it coexists with whatever else you have.

This is why plugins dominate the directory: they are composable. You can use telescope.nvim inside kickstart.nvim, inside LazyVim, or in a hand-written config, and the plugin behaves the same way.

Which one should you pick?

• Choose a pre-made configuration if you are setting up Neovim for the first time, you want a usable editor before customizing, or you would rather adjust an existing opinionated setup than build one from scratch. kickstart.nvim suits people who want a readable base to learn from; NvChad and LazyVim suit people who want a fuller experience out of the box.
• Choose individual plugins if you already have a working config and want to add one capability, you want to keep full control over keymaps and defaults, or you are replacing a single piece of an existing setup.
• Mix them if you start from a configuration and then add plugins it does not include. This is the common path: the configuration handles the baseline, and plugins fill the gaps.

A useful check before committing: open the configuration's repository and look at how many plugins it already bundles. If it covers most of what you need, adopting it is less work than assembling the same set yourself. If it covers only a fraction, starting from a minimal config plus a few plugins may be simpler.

Finding each type on neovimcraft

The directory is searchable, and the category counts are visible on the site. To browse configurations, look for the pre-made-configuration tag. To browse plugins, use a functional tag that matches your need — for example fuzzy-finder for search, lsp for language server support, or colorscheme for themes. Each listing shows stars, creation date, and last-updated date, which helps you judge whether a project is actively maintained before you build on it.

neovimcraft accepts plugin submissions through a "Submit a plugin" link on the site, and accepted entries are added to its curated directory of Neovim plugins. The directory is browsable by category — the site lists tags such as colorscheme, editing-support, lsp, git, ai, file-explorer, and many more — so before submitting, check whether your plugin already appears and which category fits it best.

What neovimcraft Is

neovimcraft describes itself as a curated Neovim plugin directory you can search through. Its homepage surfaces both plugins and pre-made configurations, for example:

The site reports 1,368 results in its plugin listing, with each entry showing stars, creation date, and last-updated date. Categories range from broad ones like colorscheme (163 entries) and editing-support (114) down to narrow ones like discord (1) and jj (1).

Before You Submit

1. Search the directory first. Use the site's search to confirm your plugin isn't already listed. Duplicate submissions are the most common reason a listing doesn't appear.
2. Pick the right category. Your plugin's primary function determines its tag. A fuzzy finder belongs under fuzzy-finder or search; a statusline plugin under statusline; a language-specific tool under programming-languages-support plus the language tag (e.g. golang, python).
3. Make sure the repository is public and installable. The directory links to GitHub repositories, so your plugin needs a public repo with a README that explains installation.

Submitting

1. Go to neovimcraft.com.
2. Find and click the "Submit a plugin" link on the page.
3. Provide your plugin's repository URL and the details the form asks for.
4. Submit and wait for review — the directory is curated, so entries are checked before appearing.

Verifying Your Submission

After submitting, search the directory for your plugin's name or browse its category tag. If it appears, the submission was accepted. If it doesn't appear after a reasonable wait, re-check that:

• The repository URL is correct and public.
• The plugin isn't already listed under a different name.
• You selected a category that matches the plugin's main purpose.

Common Snags

• Wrong category. A plugin tagged as colorscheme when it's actually a colorscheme-switcher (a separate tag with 11 entries) may be harder for users to find.
• Assuming instant listing. Because the directory is curated, submissions go through review rather than publishing immediately.
• Skipping the search step. Submitting a plugin that's already in the directory wastes the review effort and delays nothing else.

The site itself does not publish a detailed submission policy, review timeline, or acceptance criteria beyond the "Submit a plugin" option, so treat the steps above as the practical path: search first, categorize accurately, submit, then verify by searching again.

neovimcraft is a curated directory of Neovim plugins. You use it to search and browse plugins by category, and it also lists pre-made Neovim configurations. If you are looking for a plugin to solve a specific editing, LSP, or UI problem, this site is built for that kind of lookup.

What you can do on neovimcraft

• Search plugins. The site describes itself as a place to "search through our curated list of neovim plugins." The directory reports 1368 results, with stars, creation date, and last-updated date shown for each entry.
• Browse by category. Plugins are grouped into tags such as colorscheme (163), editing-support (114), programming-languages-support (108), lsp (80), utility (78), git (56), ai (52), bars-and-lines (44), code-runner (39), markdown-and-latex (38), note-taking (36), terminal-integration (36), and pre-made-configuration (35). Smaller tags include plugin-manager (10), snippet (10), completion (7), and telescope (2).
• Find pre-made configurations. The pre-made-configuration category surfaces full setups rather than single plugins. Examples listed on the site include nvim-lua/kickstart.nvim (31,524 stars, created 2022-06-23, updated 2026-09-14), described as "A launch point for your personal nvim configuration"; siduck76/NvChad (28,503 stars, created 2021-03-07, updated 2026-07-03), described as a "Blazing fast Neovim framework providing solid defaults and a beautiful UI"; and LazyVim/LazyVim.
• Submit a plugin. The site includes a "Submit a plugin" entry point, so the directory is open to additions beyond what is already indexed.

How to use it

1. Open neovimcraft.com.
2. Either type into the search field or pick a category tag that matches your need — for example, lsp if you want language server tooling, or colorscheme if you only want themes.
3. Read the result card: repository name, star count, creation date, and last-updated date. The updated date is the most useful signal for whether a plugin is still maintained.
4. Follow the link to the plugin's repository to read its own install and setup instructions. neovimcraft is a directory, not the plugin's documentation.

What it is not

neovimcraft does not host plugin code, and it does not replace each plugin's README. It also does not appear to be a package manager — installation still happens through whatever plugin manager your Neovim config uses. Treat the site as a discovery and comparison layer: it tells you what exists and roughly how popular or recent it is, then you go to the source for setup details.

When it is worth using

• You know the problem ("I want better fuzzy finding") but not the plugin name.
• You want to compare maintained options in one category without scrolling GitHub search results.
• You are starting from scratch and want to see pre-made configurations like kickstart.nvim, NvChad, or LazyVim before building your own.
• You maintain a plugin and want it listed in a curated index via the submit link.

neovimcraft is a curated directory of Neovim plugins, and you can find what you need in two ways: type a keyword into the search box, or browse the category list on the homepage. Each category shows how many plugins it contains, so you can judge at a glance whether a topic is well covered before you click into it. The directory currently lists 1,368 results.

Search by keyword

If you already know roughly what you want, search is the faster path. Enter a term such as a plugin name, a language, or a feature ("fuzzy finder", "statusline", "golang") and the directory filters the curated list down to matching entries.

What you get back is a plugin entry, not just a link. Each result shows:

• Repository name in owner/repo form, for example nvim-telescope/telescope.nvim
• Star count, a rough signal of how widely a plugin is used
• Created and updated dates, so you can tell whether a plugin is actively maintained
• A short description of what the plugin does

That combination is what makes the directory more useful than a raw GitHub search: you can compare popularity and recency side by side before opening anything.

Browse by category

The homepage lists categories with a count next to each one. The largest groups, based on the counts shown, are:

Smaller, more specific categories also exist, including debugging (25), file-explorer (26), formatting (26), fuzzy-finder (18), session (13), tmux (12), snippet (10), and plugin-manager (10). At the narrow end there are single-entry categories such as discord, jupyter, and jj.

The counts are useful for a practical reason: a category with 163 entries needs a second filter (search within it, or sort by stars), while a category with 3 entries you can just read through.

Reading a plugin entry

Entries follow a consistent format, which makes scanning fast. For example, the pre-made configuration section shows:

• nvim-lua/kickstart.nvim — 31,524 stars, created 2022-06-23, updated 2026-09-14, described as "A launch point for your personal nvim configuration"
• siduck76/NvChad — 28,503 stars, created 2021-03-07, updated 2026-07-03, described as a fast Neovim framework with solid defaults and a UI
• LazyVim/LazyVim — listed under the same pre-made-configuration category

The updated date is the field worth checking first. A high star count with an old update date tells a different story than a moderately starred plugin updated recently.

Choosing between similar plugins

When several entries in a category look equivalent, compare them on the same four fields rather than on description alone:

1. Stars — a proxy for adoption, not quality.
2. Updated date — whether the project is still receiving changes.
3. Created date — how long it has existed; a very new plugin may still be settling.
4. Description — whether it actually matches your use case, since categories are broad (for instance, utility covers 78 unrelated things).

If you are starting from nothing, the pre-made-configuration category is the place to look first, since those entries bundle many plugins together. If you already have a config and want to add one capability, go straight to the specific category — lsp, git, fuzzy-finder, formatting — and compare entries there.

Related tools on the site

The site also links to a small set of companion tools, which are separate from the plugin directory:

• nvim.sh — search for plugins from the terminal
• pgs.sh — deploy static sites with a single command
• tuns.sh — host public web services on localhost using SSH
• prose.sh — write a blog in markdown
• bower.sh — a personal blog

If you prefer not to leave Neovim to search, nvim.sh is the relevant one.

Submitting a plugin

If a plugin you use is missing, the directory has a Submit a plugin option. This is how the curated list grows, so entries are reviewed rather than crawled automatically — which is also why the counts per category are modest compared to a full GitHub search.