docs(mcp): Add PROMPTING_GUIDE.md for effective LLM discourse

PROMPTING_GUIDE.md

@@ -0,0 +1,43 @@
+# Effective Discourse: LLM Prompting Guide for MCP Memory
+
+To get the most out of the Antigravity MCP Memory server and its advanced developer tools, use specific phrases that clearly state your intent. This guides the LLM to use the most efficient tools, reducing token consumption, speeding up time-to-resolve (T2R), and avoiding brute-force file reading.
+
+## 1. Codebase Exploration & Token Efficiency
+When entering a new file, avoid having the LLM read the entire contents blindly.
+*   **Don't say:** "Read server.rs and tell me what it does." *(Consumes massive tokens)*
+*   **Do say:** "Extract the AST skeleton of server.rs to understand its structure first."
+*   **Tool Triggered:** ␍ead_file_skeleton
+
+## 2. Debugging & Log Parsing
+Stop copy-pasting giant walls of logs into the chat interface.
+*   **Don't say:** "Here is the error: [paste 500 lines of logs]"
+*   **Do say:** "The daemon crashed. Fetch the recent logs from daemon.log." or "Watch the process logs for server.log."
+*   **Tool Triggered:** get_recent_logs, watch_process_logs
+
+## 3. Git & Context Handoff
+When you've been working independently and need to loop the LLM back in on your current state.
+*   **Don't say:** "I changed some files, here are the diffs..."
+*   **Do say:** "Get the active git worktree context to review my uncommitted changes before we continue."
+*   **Tool Triggered:** get_active_worktree_context
+
+## 4. Clipboard Watch Mode (Research & Triage)
+When you are doing intense debugging across StackOverflow, logs, and docs, use the clipboard watcher to auto-ingest your breadcrumbs.
+*   **Action:** Ask the LLM to turn it on: "Enable clipboard watch mode."
+*   **Do say:** "I'm going to reproduce the bug and copy some stack traces and IDs. Give me a minute, then read my latest sticky notes to catch up."
+*   **Tool Triggered:** 	oggle_clipboard_watch_mode, followed by internal Sticky Note reads.
+
+## 5. Neovim Ghost Text (Live Previews)
+Keep your workflow entirely within your editor rather than copy-pasting code blocks from the chat.
+*   **Don't say:** "Write the updated function here so I can copy-paste it."
+*   **Do say:** "Push this refactor to my active Neovim buffer as ghost text so I can review it in-line."
+*   **Tool Triggered:** 
+vim_set_preview
+
+## 6. Graph & Memory Management
+Actively instruct the LLM to maintain its own memory constraints and organize data.
+*   **Do say:** "Log this architectural decision in the knowledge graph."
+*   **Do say:** "Add a sticky note with the test database credentials for this session."
+*   **Do say:** "Create a milestone for the 'Rich Clipboard' feature and break it down into active tasks."
+*   **Tools Triggered:** create_entities, log_decision, dd_sticky_note, dd_milestone, dd_task
+
+By phrasing requests around *actions* rather than *information retrieval*, the LLM is primed to leverage the rich MCP toolset built into the Antigravity Memory Server.

README.md

@@ -158,3 +158,4 @@ The LLM agent interacts with your active Neovim session using a dedicated set of
 - **Clipboard Watch Mode (	oggle_clipboard_watch_mode)**: Background daemon thread that auto-ingests your Ctrl+C clipboard activity directly into Knowledge Graph StickyNotes while you debug.
 - **Ghost Text Previews (
 vim_set_preview)**: Pushes proposed LLM code diffs directly into Neovim buffers as ephemeral virtual text.
+- [Prompting Guide & Effective Discourse](./PROMPTING_GUIDE.md): Learn how to phrase prompts to get the most out of the agent and memory server.