birdcc-installerlisted

# BIRD Tooling Installer Skill Guide users through installing BIRD editor support and the command-line interface toolkit. ## When to use this skill - The user asks how to install BIRD / BIRD2 / BIRD3 support in an editor. - The user asks for the VSCode / OpenVSX extension name for BIRD config. - The user asks how to install `birdcc`, `@birdcc/cli`, or the BIRD-LSP CLI. - The user wants to add BIRD syntax highlighting to Neovim, Vim, or JetBrains IDEA. - The user asks which BIRD editor plugins provide LSP versus only syntax highlighting. > For GitHub Actions or CI/CD questions, use the `birdcc-cicd` skill. ## Core principles 1. **Detect the user's editor first.** Run `scripts/detect_editor.py` and `scripts/detect_ide.py` and inspect the workspace to infer the editor. If confidence is low and the user has not named an editor, ask. See `references/editors.md` for detection cues. 2. **Default to official marketplace / OpenVSX / JetBrains Marketplace.** Provide deep links before CLI commands, and CLI commands before VSIX fallback. 3. **Do not auto-install.** Only run `scripts/detect_ide.py --install` after explicit user confirmation. 4. **Be honest about LSP vs. highlighting.** Only VSCode and VSCode forks currently have a full BIRD2 LSP extension with linting, formatting, and hover docs. Neovim and Vim only have syntax highlighting; JetBrains support depends on the BIRD plugin release status. 5. **Match the editor.** Do not assume VSCode. Provide the exact