lazyvim

Configure LazyVim Neovim setups with plugin specs and language servers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/matiacone/dotfiles --skill lazyvim-matiacone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lazyvim
Source: https://github.com/matiacone/dotfiles/tree/main/agents/.agents/skills/lazyvim
Command: npx skills add https://github.com/matiacone/dotfiles --skill lazyvim-matiacone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

LazyVim provides expert guidance to configure and tailor Neovim using the LazyVim framework, reducing setup time and confusion when enabling plugins, extras, and LSPs.

Core Features & Use Cases

  • Guided bootstrap and defaults with LazyVim and lazy.nvim
  • Craft plugin specs in lua/plugins/*.lua and merge user options with defaults
  • Troubleshoot load order, extras, and performance for large configurations

Quick Start

Use this guide to configure a minimal LazyVim setup for Neovim with a simple plugin spec.

Frequently Asked Questions about lazyvim

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a minimal LazyVim setup for Neovim?

To configure a minimal LazyVim setup, bootstrap LazyVim with lazy.nvim to establish base defaults, then define a simple plugin spec in lua/plugins/*.lua to merge user options with framework defaults.

How do I add a language server to my LazyVim configuration?

You add a language server in LazyVim by enabling the corresponding LSP extras, which configures the server automatically within the lazy.nvim loading mechanism to provide language detection and diagnostics.

What's the best way to write plugin specs for lazy loading in Neovim?

The best way to write plugin specs for lazy loading is to define them in lua/plugins/*.lua files, using detailed plugin-spec patterns to merge user configurations with LazyVim defaults and optimize load order.

Why does my plugin load order fail when troubleshooting a large LazyVim configuration?

Plugin load order fails in large LazyVim configurations due to incorrect lazy loading triggers or conflicting extras, requiring performance troubleshooting and load-order guidance to resolve dependency chains.

Can I adjust keymaps and enable extras without breaking LazyVim defaults?

You can adjust keymaps and enable extras without breaking LazyVim defaults by applying custom configurations that merge cleanly with the framework's baseline, ensuring guided bootstrap settings remain intact.

Do I need YAML frontmatter to organize LazyVim plugin directories?

You need YAML frontmatter for discovery metadata like name and description, while optional directories organize scripts, references, and assets alongside your LazyVim plugin specs.