From 7d783d2f374c4f224f8707ee156bdbe279534f22 Mon Sep 17 00:00:00 2001 From: Riz Ashraf Date: Wed, 23 Sep 2026 04:32:28 +0100 Subject: [PATCH] docs: update tool prefixes in root instructions.md --- instructions.md | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/instructions.md b/instructions.md index 10195c5..b8612a6 100644 --- a/instructions.md +++ b/instructions.md @@ -107,11 +107,6 @@ To maintain absolute traceability, we link memory items directly to the exact gi ## 15. Neovim Integration & God Mode -The project contains two MCP binaries (win-nvim and linux-nvim) that bridge JSON-RPC over stdio directly to the active Neovim instance (using ctive_nvim.txt for Last Focused Wins telemetry). -- These binaries expose basic tools ( -vim_get_cursor, -vim_get_active_buffer, -vim_list_buffers, etc.). -- **God Mode**: They also expose -vim_execute_lua. This is the ultimate fallback tool. If you need to access *any* Neovim API that does not have a dedicated Rust tool (e.g., getting LSP diagnostics, evaluating a visual selection block based on modes, setting registers), you MUST write a short Lua script and pass it to -vim_execute_lua. Do not attempt to recompile the Rust server to add new basic tools; use the Lua escape hatch dynamically. +The project contains two MCP binaries (win-nvim and linux-nvim) that bridge JSON-RPC over stdio directly to the active Neovim instance (using `active_nvim.txt` for Last Focused Wins telemetry). +- These binaries expose basic tools (`nvim_get_cursor`, `nvim_get_active_buffer`, `nvim_list_buffers`, etc.). +- **God Mode**: They also expose `nvim_execute_lua`. This is the ultimate fallback tool. If you need to access *any* Neovim API that does not have a dedicated Rust tool (e.g., getting LSP diagnostics, evaluating a visual selection block based on modes, setting registers), you MUST write a short Lua script and pass it to `nvim_execute_lua`. Do not attempt to recompile the Rust server to add new basic tools; use the Lua escape hatch dynamically.