world

This skill provides a comprehensive interface for managing Neovim as part of a modular, reproducible dotfile system. It is designed for power users and software engineers who treat their development environment as code. The skill facilitates deep integration with Neovim, allowing users to modularize configuration files, manage dependencies using native vim.pack functionality, and streamline the build process for custom, portable Neovim releases. Whether you are configuring LSP settings, treesitter queries, or managing complex daemon-based workflows, this skill offers the necessary logic to maintain a consistent environment across multiple architectures, including Darwin-arm64 and Linux-x64.

• Full support for modular Neovim configuration via .config/nvim/plugin/ files, ensuring clean and organized feature separation.

• Built-in management for custom Neovim nightly builds, utilizing reproducible lock files (nvim-pack-lock.json) and automated workflows to bundle plugins into portable tarballs.

• Native Neovim daemon orchestration, allowing users to start, stop, and status-check headless instances via the nvimd wrapper, with multi-socket support for isolated project environments.

• Advanced keybinding and environment management, favoring native Lua configurations and minimal reliance on external plugin managers.

• Cross-platform portability, specifically optimized for environments using the world monorepo structure and cosmopolitan-linked utilities.

• Inputs include path-specific Lua configuration files, plugin metadata in lock files, and CLI commands for daemon control.

• Expected outputs range from generated environment-specific binaries and plugin bundles to real-time status reports of Neovim server sockets.

• Always prefer Lua for configuration logic; avoid legacy Vimscript where possible to maintain consistency with the repository architecture.

• Utilize vim.pack.add() for plugin management, keeping in mind the constraints of the local site/pack/core/opt directory structure.

• When building releases, ensure the luajit bootstrap is active to support the necessary JSON and plugin-fetching dependencies found in the build scripts.