lsp-routinglisted

# LSP Routing ## Purpose Choose the correct language-server workflow before coding. The goal is accurate diagnostics, semantic navigation, and low-entropy implementation without pretending every file type is Serena-native. User-facing conversation stays Russian unless requested otherwise. Repository docs and plugin files stay English. ## When To Use Use this skill when a task involves: - LSPs, language servers, diagnostics, type checking, symbol navigation, code intelligence, or semantic refactoring. - Project setup for Python, Rust, Dart, Flutter, TypeScript, JavaScript, Go, C, C++, Qt, QML, YAML, Docker, HTML, CSS, Shell, JSON, TOML, or Markdown. - Choosing whether Serena MCP can provide semantic tools for a file type. - Preparing a high-quality implementation where language-server feedback matters. ## Routing Rules 1. Detect the language from files, manifests, lockfiles, and build files, not from file extensions alone when project structure matters. 2. Read `${CLAUDE_PLUGIN_ROOT}/references/lsp-server-matrix.md` when exact command names, Serena keys, or prerequisites matter. 3. Use `serena-lsp-integration` when the question affects Serena project languages, `.serena/project.yml`, `ls_specific_settings`, or `serena project index`. 4. Use `lsp-health-check` when the user asks whether LSPs work, when a project has missing diagnostics, or before non-trivial code work in a newly seen stack. 5. Use `lsp-setup` only after an explicit user request to install or update tool