lsp-setuplisted

# LSP Setup for Claude Code Projects Set up Language Server Protocol support in Claude Code for the current project. This enables semantic code intelligence: go-to-definition, find-references, hover, document symbols, workspace symbols, diagnostics, and call hierarchy — all at ~50ms instead of 30-60s grep-based navigation. ## State Detection This skill operates as a state machine. On each invocation, detect the current state and resume from the appropriate step: 1. **No LSP configured** → Start from Step 1 (detect languages) 2. **Binaries missing** → Resume at Step 3 (install binaries) 3. **Plugins not installed** → Resume at Step 4 (install plugins) 4. **Plugins installed but LSP returns "No LSP server available"** → Step 5 (restart needed) 5. **LSP responds with symbols** → Step 6 (validation complete, report success) To detect state quickly: attempt an `LSP documentSymbol` call on any source file in the project. If it returns results, skip to validation. If "No LSP server available", check whether plugins are installed and binaries are on PATH. ## Step 1: Detect Environment Determine the current environment by checking `uname -s`: - `MINGW*` or `MSYS*` → MINGW (Git Bash on Windows) - `/proc/version` contains "microsoft" → WSL - `Darwin` → macOS - Otherwise → Linux This affects install commands and PATH gotchas. Consult `references/gotchas.md` for environment-specific issues. ## Step 2: Detect Languages Scan the current project directory for language indicators us