Skip to main content
prompt GP ChatGPT

Neovim Config taste — ChatGPT prompt: what it does

The Neovim Config taste ChatGPT prompt sets out a terminal-first style for building a Neovim configuration in Lua. It covers plugin loading, language tools, formatting, and key bindings.

CC0-1.0 ★ 178,201 updated 2026-10-24

Open on GitHub

What Neovim Config taste does

The prompt lays out a Neovim setup that starts in init.lua and loads small modules from lua/config and lua/plugins. It uses lazy.nvim and commits lazy-lock.json to pin plugin versions. Plugins load on events, commands, filetypes, or key presses; startup time is measured with :Lazy profile, with a target below 50 ms.

For language support, it favors Neovim’s built-in LSP client with nvim-lspconfig and uses mason.nvim to install servers and tools. conform.nvim handles formatting on save, while nvim-lint runs lint checks using the project’s CI settings. The prompt also covers Treesitter, a single fuzzy finder, Git signs, and grouped mappings.

A Neovim configuration written in Lua is required. The finder and completion options are choices rather than a fixed stack: use telescope.nvim or fzf-lua, and either Neovim’s built-in completion or blink.cmp. Machine-specific settings go in a Git-ignored local.lua.

What it helps with

  • split a Neovim setup into Lua modules
  • pin plugin versions with lazy-lock.json
  • match editor formatting and linting to CI
  • organize mappings for search, Git, and LSP

Example prompts for the agent

  • Create a Lua Neovim setup with modules under lua/config and lua/plugins.
  • Configure lazy.nvim, LSP, and save-time formatting using these preferences.
  • Group mappings for search, Git, and LSP without replacing core Vim motions.

How to install Neovim Config taste

How to use

Paste the text at the start of a chat or into project instructions

Questions about Neovim Config taste

How do I install Neovim Config taste in Claude Code?

Place the prompt file at .claude/commands/prompts.csv.md.

What does Neovim Config taste do?

It describes a modular Lua setup for Neovim, including plugin management, LSP, formatting, linting, and key mappings.

Which finder and completion plugins does Neovim Config taste suggest?

It offers telescope.nvim or fzf-lua for finding, and Neovim’s built-in completion or blink.cmp for completion.

Source text

prompts.csv · CC0-1.0
# Neovim Config taste of a minimalist terminal-first developer
- Write the whole config in Lua, starting from a single init.lua that requires small modules under lua/config and lua/plugins. Confidence: 0.90
- Use lazy.nvim as the plugin manager and commit lazy-lock.json so every machine gets the same plugin versions. Confidence: 0.90
- Lazy-load plugins by event, command, filetype or key mapping, and keep startup time under 50 ms measured with :Lazy profile. Confidence: 0.80
- Prefer the built-in LSP client with nvim-lspconfig over heavier all-in-one language plugins. Confidence: 0.85
- Install language servers, formatters and linters with mason.nvim, but pin the tool list in config instead of installing by hand. Confidence: 0.80
- Format on save with conform.nvim and lint with nvim-lint, using the same tools and settings the project runs in CI. Confidence: 0.85
- Use nvim-treesitter for highlighting, indentation and text objects, and list the parsers you need explicitly. Confidence: 0.85
- Pick one fuzzy finder, such as telescope.nvim or fzf-lua, and route files, grep, buffers and LSP symbols through it. Confidence: 0.85
- Set the leader key to space before loading any plugin so every mapping uses it. Confidence: 0.90
- Give every custom mapping a desc field so which-key and :map show what it does. Confidence: 0.85
- Group mappings by prefix, like leader f for find, leader g for git and leader l for LSP, and avoid overriding core Vim motions. Confidence: 0.80
- Keep options in one options.lua file using vim.opt, with a short comment for anything that is not obvious. Confidence: 0.80
- Use relative line numbers, a sign column that is always shown, and persistent undo files. Confidence: 0.75
- Use autocommand groups with clear = true so reloading the config never duplicates handlers. Confidence: 0.90
- Respect .editorconfig files and avoid hard-coding indentation per language unless a project has no settings. Confidence: 0.80
- Show git changes in the sign column with gitsigns.nvim and stage hunks from the editor. Confidence: 0.80
- Use the built-in completion engine or blink.cmp, with LSP and snippet sources only, to keep the popup fast and relevant. Confidence: 0.70
- Choose one colorscheme with good Tree-sitter and LSP semantic token support, and do not chase new themes every week. Confidence: 0.65
- Add a plugin only when it replaces a repeated manual step, and remove plugins you have not used in a month. Confidence: 0.80
- Keep machine-specific settings in a git-ignored local.lua file so the main config stays portable. Confidence: 0.75
- Run :checkhealth after upgrades and fix warnings before adding new plugins. Confidence: 0.80
- Store the config in a dotfiles repository and upgrade plugins deliberately, reviewing the lazy.nvim changelog first. Confidence: 0.85

© f · CC0-1.0 · f/prompts.chat

Similar prompts

All prompts for Data and databases →

From the same set218

The whole set →
Playwright E2E taste The Playwright E2E taste prompt for ChatGPT sets conventions for Playwright end-to-end tests. It covers core user journeys and test isolation, from local runs to CI. GP ChatGPT ★ 178,201repo stars Next.js App taste Next.js App taste — a prompt for ChatGPT and Claude.ai that enforces pragmatic Next.js App Router conventions. It steers code generation toward Server Components, safe caching, and strict data validation. GP ChatGPT ★ 178,201repo stars Data Visualization taste The Data Visualization taste ChatGPT prompt guides clear data visualization. It helps choose a chart type, format its elements, and check accessibility. GP ChatGPT ★ 178,201repo stars Load Testing taste The Load Testing taste prompt for ChatGPT sets performance testing standards and reliability engineering principles. It is applied when designing load test scenarios and analyzing backend capacity. GP ChatGPT ★ 178,201repo stars API Client SDK taste API Client SDK taste — a prompt for ChatGPT that defines developer-experience standards for building API client SDKs. It runs during API architecture design, OpenAPI code generation, and error-handling setup. GP ChatGPT ★ 178,201repo stars dbt Analytics Project taste dbt Analytics Project taste — a prompt for ChatGPT sets conventions for dbt models, tests, documentation, and CI. Use it while shaping an analytics project or revising its model structure. GP ChatGPT ★ 178,201repo stars Design System taste Design System taste — a prompt for ChatGPT that enforces pragmatic design system standards, tokens, accessibility, and component architecture. GP ChatGPT ★ 178,201repo stars Unity Game Project taste Unity Game Project taste — a prompt for ChatGPT that sets engineering guidelines for Unity game projects. It covers code structure, assets, testing, and builds. GP ChatGPT ★ 178,201repo stars

Project sponsors

Companies that keep this analytics open