content/skills/tech-stack-skills/lsp-manager/SKILL.md
Detect project languages, configure LSP servers, and troubleshoot language-server integration. Use this skill when setting up code intelligence, autocomplete, type checking, IDE integration, or diagnosing LSP failures — prefer it over manual config for any language-server task.
npx skillsauth add bahayonghang/my-claude-code-settings lsp-managerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Execute the LSP configuration or troubleshooting task described in $ARGUMENTS.
$ARGUMENTS is empty, report an error requesting the user to specify their project path or language.python $SKILL_DIR/scripts/detect_language.py <target_directory>.python $SKILL_DIR/scripts/check_server.py.python $SKILL_DIR/scripts/generate_config.py <Languages...>.$SKILL_DIR/references/servers.md and $SKILL_DIR/references/troubleshooting.md if specific servers or troubleshooting steps are needed.Information about the detected languages, recommended LSP servers, or instructions for fixing integration issues.
$SKILL_DIR/references/troubleshooting.md for guidance on how to fix common problems before presenting them to the user.development
Turn vague or complex Codex tasks into strong `/goal` commands with outcome, verification, constraints, boundaries, iteration policy, completion evidence, and pause/block conditions. Use when the user asks for Codex goal instructions, Goal 指令, 目标指令, `/goal` prompts, 中文 Goal 模板, plan-to-goal interviews, success criteria, verification commands, or bounded agent work definitions.
tools
Write, debug, and validate ast-grep structural code search rules. Use this skill when the user needs syntax-aware code search, AST pattern matching, structural refactor discovery, language-construct queries, or searches that plain text tools like rg can miss, such as finding functions with particular descendants, calls inside specific contexts, missing error handling, React hook shapes, decorators, or other Tree-sitter-backed code structures.
development
Use when the user asks to ground an ambitious proposal, avoid over-grand designs, make a bold direction executable, pressure-test feasibility, prevent "too much vision and too little landing", or turn a strategy/refactor/product idea into the smallest verifiable first move with stop rules. Trigger for requests such as 落地, 先落地, 别太飘, 收一收, 可执行, 可验证, 止损, and for follow-ups after geju-style big-picture thinking. Do not trigger for ordinary code review or implementation unless the user explicitly asks to ground or shrink the plan first.
development
Use when the user explicitly asks to think bigger, open up the design space, challenge conservative design, avoid over-indexing on backward compatibility, escape local-detail fixation, or make a bold high-level product or architecture direction call. Use for strategic reframing, not for ordinary code review, PRD writing, implementation planning, or adversarial risk review.