원클릭으로 Manus에서 모든 스킬 실행

lsp-routing

스타1

포크0

업데이트2026년 6월 12일 10:36

Маршрутизация LSP: type checking, symbols, diagnostics, refactor. Используй для: типы, символы. EN: language server routing.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

NDDev-it-com

NDDev-it-com/rldyour-codex

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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.

Auto Invocation

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

Detect the language from files, manifests, lockfiles, and build files, not from file extensions alone when project structure matters.
Read references/lsp-server-matrix.md when exact command names, Serena keys, or prerequisites matter.
Use serena-lsp-integration when the question affects Serena project languages, .serena/project.yml, ls_specific_settings, or serena project index.
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.
Use lsp-setup only after an explicit user request to install or update tools.

Default Decisions

Python: Pyright for semantic analysis, Ruff as companion lint/format tooling.
TypeScript and JavaScript: typescript-language-server by default. Use typescript_vts or vtsls only when explicitly requested or project evidence requires it.
Rust: rust-analyzer and rust-src.
Dart and Flutter: Dart SDK analyzer, with Flutter SDK awareness for Flutter projects.
Go: gopls only inside a real module or workspace.
C, C++, Qt C++: clangd and compile_commands.json.
Qt QML: qmlls externally; do not claim Serena-native QML support.
YAML: yaml-language-server plus schemas.
Docker: Docker Language Server externally.
HTML/CSS/JSON: vscode-langservers-extracted.
Shell: bash-language-server plus shellcheck.
TOML: Taplo.
Markdown: Marksman.

Runtime Safety

Do not start a stdio language server manually unless a real LSP client controls the session. For checks, verify command availability, versions, and project prerequisites.

Do not use first-run bunx or uvx as a long-lived LSP runtime. Use stable local executables. Package managers are allowed for explicit setup and health checks.

이 저장소의 다른 Skills

같은 저장소

browser-debug

NDDev-it-com/rldyour-codex

Отлаживает browser-only failures через Chrome DevTools MCP и Playwright CLI. Используй для: консоль, сеть, runtime, layout, memory, performance, Lighthouse. EN triggers: browser debug, console, network, runtime, performance.

2026-07-101

browser-tool-routing

NDDev-it-com/rldyour-codex

Маршрутизирует browser tasks только через managed Playwright CLI и Chrome DevTools MCP. Используй для: UI, визуально, скриншот, Figma, консоль, сеть, перфоманс. EN triggers: browser routing, UI validation, screenshots, visual QA, console, network.

2026-07-101

browser-validation

NDDev-it-com/rldyour-codex

Валидирует UI и сценарии через Playwright CLI evidence. Используй для: проверь UI, браузер, скриншот, регрессия, адаптив, бизнес-логика, визуально. EN triggers: validate UI, browser check, regression, responsive, screenshot.

2026-07-101

playwright-cli-validation

NDDev-it-com/rldyour-codex

Низкоуровневая browser automation через Playwright CLI. Используй для: screenshots, snapshots, headed sessions, traces, responsive, UI proof. EN triggers: Playwright CLI validation, screenshots, snapshots, traces.

2026-07-101

visual-diff-review

NDDev-it-com/rldyour-codex

Проводит visual QA для Figma, screenshots и reference images. Используй для: pixel-perfect, сравни с Figma, сравни с фото, diff. EN triggers: visual diff, pixel-perfect, compare Figma, reference image.

2026-07-101

webwright-task

NDDev-it-com/rldyour-codex

Маршрутизирует старые Webwright-запросы в управляемые CloakBrowser workflows. Используй для: длинная web-задача, RPA, extraction. EN triggers: compatibility browser task, long-horizon web task.

2026-07-101

name	lsp-routing
description	Маршрутизация LSP: type checking, symbols, diagnostics, refactor. Используй для: типы, символы. EN: language server routing.

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.

Auto Invocation

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

Detect the language from files, manifests, lockfiles, and build files, not from file extensions alone when project structure matters.
Read references/lsp-server-matrix.md when exact command names, Serena keys, or prerequisites matter.
Use serena-lsp-integration when the question affects Serena project languages, .serena/project.yml, ls_specific_settings, or serena project index.
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.
Use lsp-setup only after an explicit user request to install or update tools.

Default Decisions

Python: Pyright for semantic analysis, Ruff as companion lint/format tooling.
TypeScript and JavaScript: typescript-language-server by default. Use typescript_vts or vtsls only when explicitly requested or project evidence requires it.
Rust: rust-analyzer and rust-src.
Dart and Flutter: Dart SDK analyzer, with Flutter SDK awareness for Flutter projects.
Go: gopls only inside a real module or workspace.
C, C++, Qt C++: clangd and compile_commands.json.
Qt QML: qmlls externally; do not claim Serena-native QML support.
YAML: yaml-language-server plus schemas.
Docker: Docker Language Server externally.
HTML/CSS/JSON: vscode-langservers-extracted.
Shell: bash-language-server plus shellcheck.
TOML: Taplo.
Markdown: Marksman.

Runtime Safety

Do not start a stdio language server manually unless a real LSP client controls the session. For checks, verify command availability, versions, and project prerequisites.

Do not use first-run bunx or uvx as a long-lived LSP runtime. Use stable local executables. Package managers are allowed for explicit setup and health checks.