feat: add Go LSP configuration and code navigation documentation

ThomasK33 · ThomasK33 · commit 9415189b9d03 · 2025-06-26T18:59:46.000+02:00
Change-Id: I994c8ee8fa2c246808a9f68a86e83a6a3db6f8ac
Signed-off-by: Thomas Kosiewski &lt;tk@coder.com&gt;
diff --git a/CLAUDE.md b/CLAUDE.md
@@ -270,6 +270,50 @@ if errors.Is(err, errInvalidPKCE) {
 - Test both positive and negative cases
 - Use `testutil.WaitLong` for timeouts in tests
 
+## Code Navigation and Investigation
+
+### Using Go LSP Tools
+
+When working with the Coder codebase, leverage Go Language Server Protocol tools for efficient code navigation:
+
+1. **Find function definitions**:
+
+   ```
+   mcp__go-language-server__definition symbolName
+   ```
+
+   - Example: `mcp__go-language-server__definition getOAuth2ProviderAppAuthorize`
+   - Quickly jump to function implementations across packages
+
+2. **Find symbol references**:
+
+   ```
+   mcp__go-language-server__references symbolName
+   ```
+
+   - Locate all usages of functions, types, or variables
+   - Understand code dependencies and call patterns
+
+3. **Get symbol information**:
+
+   ```
+   mcp__go-language-server__hover filePath line column
+   ```
+
+   - Get type information and documentation at specific positions
+
+4. **When to use LSP vs other tools**:
+   - **Use LSP for**: Following function calls, understanding package relationships, finding specific implementations
+   - **Use Grep for**: Text-based searches, finding patterns across files
+   - **Use Bash for**: Simple file operations, running tests, git commands
+
+### Investigation Strategy
+
+1. **Start with route registration** in `coderd/coderd.go` to understand API endpoints
+2. **Use LSP definition lookup** to trace from route handlers to actual implementations
+3. **Follow the middleware chain** to understand request processing flow
+4. **Check test files** for expected behavior and error patterns
+
 ## Testing Scripts
 
 ### OAuth2 Test Scripts
