Writing Lua

Modular architecture separates concerns into single-responsibility modules: init.lua for entry, operations.lua for logic, display.lua for UI, config.lua for settings, and utils.lua for helpers. This prevents tight coupling, improves testability, and makes plugins maintainable as complexity grows.

LuaCATS annotations add type safety to Lua code, enabling IDE autocomplete, catching errors before runtime, and improving code reliability. For Neovim plugins, they document function signatures and reduce bugs in coordinate handling and API calls.

Performance optimization applies lazy loading to defer module initialization, implements caching for repeated operations, and uses debouncing for high-frequency events. These techniques reduce plugin load time and prevent editor slowdown.

Yes, test-driven development with Plenary provides a Lua testing framework integrated with Neovim's plugin ecosystem. It enables unit tests for plugin logic, configuration handlers, and coordinate transformations before deployment.

Neovim uses 0-indexed coordinates internally but 1-indexed for user-facing display. The pattern converts between systems: store and process with 0-indexing internally, convert to 1-indexed when displaying or accepting user input.

Separate keymap and command definitions into a dedicated config.lua module with clear registration patterns. This centralizes user-facing bindings, simplifies rebinding, and keeps plugin logic decoupled from input handling.