@litfamily/lithermes 1.0.0

package/assets/lithermes-plugin/skills/lsp-setup/references/haskell/README.md

@@ -0,0 +1,69 @@
+# Haskell — LSP setup (Hermes / LitHermes)
+
+- **Recommended server:** `haskell-language-server-wrapper --lsp`
+- **Extensions:** `.hs .lhs`
+- **Install hint:** `ghcup install hls`
+
+The `-wrapper` binary detects your project's GHC version and dispatches to the matching HLS build.
+
+## Install
+
+- **macOS:** `ghcup install hls` (install ghcup via `brew install ghcup` or the official script)
+- **Linux:** `ghcup install hls` (ghcup script from https://www.haskell.org/ghcup/)
+- **Windows:** `ghcup install hls` (ghcup is installed via the Windows installer / PowerShell bootstrap)
+
+HLS needs a working GHC plus Cabal and/or Stack. Install a matching toolchain first:
+
+```bash
+ghcup install ghc
+ghcup install cabal
+```
+
+Confirm it resolves:
+
+```bash
+command -v haskell-language-server-wrapper
+```
+
+## Configure
+
+Add a `haskell` entry to the Hermes LSP config under `lsp.<language>`:
+
+```json
+{
+  "lsp": {
+    "haskell": {
+      "command": [
+        "haskell-language-server-wrapper",
+        "--lsp"
+      ],
+      "extensions": [
+        ".hs",
+        ".lhs"
+      ]
+    }
+  }
+}
+```
+
+Hermes routes `.hs`/`.lhs` edits to the HLS wrapper via the `extensions` list. Per-project
+plugin/formatter settings normally live in a `hie.yaml` (cradle) and
+`.haskell-language-server` files rather than the Hermes LSP config.
+
+## Alternatives
+
+- `ghcide` (the core HLS engine, standalone) — largely superseded by HLS.
+- `hlint` standalone for lint-only checks; `ormolu`/`fourmolu` for formatting.
+
+## Troubleshooting
+- **PATH:** `haskell-language-server-wrapper` on PATH; reopen shell after `ghcup install`.
+- **GHC mismatch:** the installed HLS must support your project's GHC version — run `ghcup install hls` for that GHC, or align GHC to a supported one.
+- **No cradle:** multi-package repos may need a `hie.yaml`; generate one with `gen-hie > hie.yaml`.
+- **Slow first load:** HLS compiles dependencies on first open; let it finish indexing.
+
+## Verify
+
+```bash
+node --experimental-strip-types ../../scripts/verify-lsp.ts path/to/file.hs
+# or: bun ../../scripts/verify-lsp.ts path/to/file.hs
+```

package/assets/lithermes-plugin/skills/lsp-setup/references/java/README.md

@@ -0,0 +1,70 @@
+# Java — LSP setup (Hermes / LitHermes)
+
+- **Recommended server:** `jdtls`
+- **Extensions:** `.java`
+- **Install hint:** `https://github.com/eclipse-jdtls/eclipse.jdt.ls`
+
+## Install
+
+- **macOS:** `brew install jdtls`
+- **Linux:** Download from [eclipse-jdtls/eclipse.jdt.ls](https://github.com/eclipse-jdtls/eclipse.jdt.ls) releases, extract, and wrap the launcher as `jdtls` on PATH (some distros package it as `jdtls`/`jdt-language-server`).
+- **Windows:** Download the release archive and add the `jdtls` launcher (`bin/jdtls.bat` or the Python wrapper) to PATH.
+
+Requires a **JDK 17+** to run the language server itself (the project may target an older Java version).
+
+Confirm it resolves:
+
+```bash
+command -v jdtls
+```
+
+## Configure
+
+Add a `java` entry to the Hermes LSP config under `lsp.<language>`:
+
+```json
+{
+  "lsp": {
+    "java": {
+      "command": [
+        "jdtls"
+      ],
+      "extensions": [
+        ".java"
+      ]
+    }
+  }
+}
+```
+
+Hermes routes `.java` edits to `jdtls` via the `extensions` list. jdtls maintains
+a per-project workspace data directory and the first index is slow (it resolves
+the full classpath and builds). If `jdtls` cannot find a runtime, export
+`JAVA_HOME` for a JDK 17+ in the shell that launches Hermes:
+
+```bash
+export JAVA_HOME=/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home
+```
+
+Most settings (runtimes, format, import order) come from `settings.java.*`
+defaults and work for Maven/Gradle projects with a standard layout.
+
+## Alternatives
+
+**No mainstream alternative.** `jdtls` (Eclipse JDT Language Server) is the
+de-facto standard and powers the official VS Code Java extension.
+
+## Troubleshooting
+
+- **PATH:** `jdtls` on PATH; reopen shell after install.
+- **No JDK found:** server exits immediately — set `JAVA_HOME` to a JDK 17+.
+- **Slow / no completions at first:** the initial classpath index can take a minute or more on large Maven/Gradle projects; wait for it to finish.
+- **Stale state:** delete the jdtls workspace data dir to force a clean re-index if results go wrong after big dependency changes.
+- **Build tool required:** keep `pom.xml` / `build.gradle` valid; a broken build descriptor breaks symbol resolution.
+
+## Verify
+
+```bash
+node --experimental-strip-types ../../scripts/verify-lsp.ts path/to/File.java
+# or: bun ../../scripts/verify-lsp.ts path/to/File.java
+```

package/assets/lithermes-plugin/skills/lsp-setup/references/julia/README.md

@@ -0,0 +1,70 @@
+# Julia — LSP setup (Hermes / LitHermes)
+
+- **Recommended server:** `julia --startup-file=no --history-file=no -e "using LanguageServer; runserver()"`
+- **Extensions:** `.jl`
+- **Install hint:** `julia -e 'using Pkg; Pkg.add("LanguageServer")'`
+
+The PATH executable is `julia`; LanguageServer.jl is launched through the `-e` snippet, not as its own binary.
+
+## Install
+
+Install Julia (juliaup recommended), then add the `LanguageServer` package:
+
+- **macOS:** `brew install juliaup && juliaup add release`
+- **Linux:** `curl -fsSL https://install.julialang.org | sh` (installs juliaup)
+- **Windows:** `winget install julia -s msstore` (installs juliaup)
+
+Then add the package — ideally into a shared `@lsp` environment so it is not tied to one project:
+
+```bash
+julia --project=@lsp -e 'using Pkg; Pkg.add("LanguageServer")'
+```
+
+Confirm Julia resolves (the LSP binary IS `julia`):
+
+```bash
+command -v julia
+```
+
+## Configure
+
+Add a `julia` entry to the Hermes LSP config under `lsp.<language>`:
+
+```json
+{
+  "lsp": {
+    "julia": {
+      "command": [
+        "julia",
+        "--startup-file=no",
+        "--history-file=no",
+        "-e",
+        "using LanguageServer; runserver()"
+      ],
+      "extensions": [
+        ".jl"
+      ]
+    }
+  }
+}
+```
+
+Hermes routes `.jl` edits to the Julia language server via the `extensions` list. To pin
+which environment hosts LanguageServer.jl, export `JULIA_PROJECT=@lsp` in the
+shell that launches Hermes.
+
+## Alternatives
+
+- The VS Code Julia extension bundles the same LanguageServer.jl server.
+
+## Troubleshooting
+- **PATH:** `julia` on PATH (not a `julials` binary); reopen shell after juliaup install.
+- **First run precompiles — be patient:** the initial launch compiles LanguageServer.jl and may take minutes with no output; do not kill it. Subsequent starts are fast.
+- **Package not found:** `LanguageServer` must be installed in the environment the server runs in (e.g. `@lsp`); add it there and set `JULIA_PROJECT`.
+
+## Verify
+
+```bash
+node --experimental-strip-types ../../scripts/verify-lsp.ts path/to/file.jl
+# or: bun ../../scripts/verify-lsp.ts path/to/file.jl
+```

package/assets/lithermes-plugin/skills/lsp-setup/references/kotlin/README.md

@@ -0,0 +1,72 @@
+# Kotlin — LSP setup (Hermes / LitHermes)
+
+- **Recommended server:** `kotlin-lsp`
+- **Extensions:** `.kt .kts`
+- **Install hint:** `https://github.com/Kotlin/kotlin-lsp`
+
+## Install
+
+The official **JetBrains Kotlin LSP** is pre-release. Download a build from the [Kotlin/kotlin-lsp](https://github.com/Kotlin/kotlin-lsp) releases and put the `kotlin-lsp` launcher on PATH.
+
+- **macOS:** Download the release archive, extract, then symlink the launcher: `ln -s /path/to/kotlin-lsp/kotlin-lsp.sh /usr/local/bin/kotlin-lsp`
+- **Linux:** Same as macOS — extract the release and place/symlink `kotlin-lsp` on PATH.
+- **Windows:** Extract the release and add the directory containing `kotlin-lsp.bat` to PATH (invoke as `kotlin-lsp`).
+
+Requires a **JDK** on the machine to run the server.
+
+Confirm it resolves:
+
+```bash
+command -v kotlin-lsp
+```
+
+## Configure
+
+Add a `kotlin` entry to the Hermes LSP config under `lsp.<language>`:
+
+```json
+{
+  "lsp": {
+    "kotlin": {
+      "command": [
+        "kotlin-lsp"
+      ],
+      "extensions": [
+        ".kt",
+        ".kts"
+      ]
+    }
+  }
+}
+```
+
+Hermes routes `.kt`/`.kts` edits to `kotlin-lsp` via the `extensions` list. If the server
+cannot find a Java runtime, export `JAVA_HOME` in the launching shell:
+
+```bash
+export JAVA_HOME=/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home
+```
+
+The server resolves classpath from Gradle/Maven; keep the build descriptor
+importable.
+
+## Alternatives
+
+**`fwcd/kotlin-language-server`** — older community server. Still usable but less
+actively maintained than the official JetBrains one; set the `command` to its
+launcher if you prefer it.
+
+## Troubleshooting
+
+- **PATH:** `kotlin-lsp` on PATH; reopen shell after install.
+- **Pre-release churn:** the JetBrains server is early; pin a known-good release and expect occasional breakage.
+- **No JDK:** server fails to start — install a JDK and/or set `JAVA_HOME`.
+- **Slow first import:** Gradle resolution on first open can be slow on large projects; let it complete.
+- **`.kts` scripts:** build/script files resolve more slowly than `.kt` sources; this is expected.
+
+## Verify
+
+```bash
+node --experimental-strip-types ../../scripts/verify-lsp.ts path/to/File.kt
+# or: bun ../../scripts/verify-lsp.ts path/to/File.kt
+```

package/assets/lithermes-plugin/skills/lsp-setup/references/lua/README.md

@@ -0,0 +1,68 @@
+# Lua — LSP setup (Hermes / LitHermes)
+
+- **Recommended server:** `lua-language-server`
+- **Extensions:** `.lua`
+- **Install hint:** `https://github.com/LuaLS/lua-language-server`
+
+## Install
+
+See `https://github.com/LuaLS/lua-language-server`.
+
+- **macOS:** `brew install lua-language-server`
+- **Linux:** download a release from GitHub, or `pacman -S lua-language-server` (Arch) / AUR
+- **Windows:** download a release from the GitHub releases page and add its `bin` to PATH
+
+Confirm it resolves:
+
+```bash
+command -v lua-language-server
+```
+
+## Configure
+
+Add a `lua` entry to the Hermes LSP config under `lsp.<language>`:
+
+```json
+{
+  "lsp": {
+    "lua": {
+      "command": [
+        "lua-language-server"
+      ],
+      "extensions": [
+        ".lua"
+      ]
+    }
+  }
+}
+```
+
+Hermes routes `.lua` edits to `lua-language-server` via the `extensions` list. Deeper
+behavior (Neovim runtime libraries, the Lua runtime version, allowed globals)
+is configured through a project `.luarc.json` rather than the Hermes LSP config. For
+Neovim config work, a `.luarc.json` like the following resolves `vim` globals and
+the stdlib:
+
+```json
+{
+  "runtime": { "version": "LuaJIT" },
+  "workspace": { "library": ["/usr/share/nvim/runtime/lua"] },
+  "diagnostics": { "globals": ["vim"] }
+}
+```
+
+## Alternatives
+
+None.
+
+## Troubleshooting
+- **PATH:** `lua-language-server` must be on PATH; reopen the shell after install.
+- **Undefined `vim` global:** add `vim` to `diagnostics.globals` and set `workspace.library` in `.luarc.json` (see above) for Neovim work.
+- **Wrong runtime version:** set `runtime.version` (`LuaJIT`, `Lua 5.4`, etc.) to match your interpreter, or stdlib functions report as undefined.
+
+## Verify
+
+```bash
+node --experimental-strip-types ../../scripts/verify-lsp.ts path/to/file.lua
+# or: bun ../../scripts/verify-lsp.ts path/to/file.lua
+```

package/assets/lithermes-plugin/skills/lsp-setup/references/php/README.md

@@ -0,0 +1,61 @@
+# PHP — LSP setup (Hermes / LitHermes)
+
+- **Recommended server:** `intelephense --stdio`
+- **Extensions:** `.php`
+- **Install hint:** `npm install -g intelephense`
+
+## Install
+
+Intelephense is a Node package, so Node.js (and npm) must be installed first.
+
+- **macOS:** `npm install -g intelephense`
+- **Linux:** `npm install -g intelephense`
+- **Windows:** `npm install -g intelephense`
+
+Confirm it resolves:
+
+```bash
+command -v intelephense
+```
+
+## Configure
+
+Add a `php` entry to the Hermes LSP config under `lsp.<language>`:
+
+```json
+{
+  "lsp": {
+    "php": {
+      "command": [
+        "intelephense",
+        "--stdio"
+      ],
+      "extensions": [
+        ".php"
+      ]
+    }
+  }
+}
+```
+
+Hermes routes `.php` edits to `intelephense` via the `extensions` list. Intelephense's
+premium features (rename, find-all-implementations, etc.) require a licence key,
+which is passed through the editor's LSP `initializationOptions` rather than
+the Hermes LSP config. Without a key the server runs fine in free mode.
+
+## Alternatives
+
+**phpactor** — pure-PHP, no Node dependency. Set the `command` to
+`["phpactor", "language-server"]`.
+
+## Troubleshooting
+- **PATH:** `intelephense` must be on PATH; reopen the shell after a global npm install. If missing, check `npm bin -g` is on PATH.
+- **No Node:** Intelephense fails to start without Node.js. Install Node, then reinstall.
+- **Wrong PHP version inference:** set `intelephense.environment.phpVersion` (via your editor's init options) to match your project.
+
+## Verify
+
+```bash
+node --experimental-strip-types ../../scripts/verify-lsp.ts path/to/file.php
+# or: bun ../../scripts/verify-lsp.ts path/to/file.php
+```

package/assets/lithermes-plugin/skills/lsp-setup/references/python/README.md

@@ -0,0 +1,73 @@
+# Python — LSP setup (Hermes / LitHermes)
+
+- **Recommended server:** `basedpyright-langserver --stdio`
+- **Extensions:** `.py .pyi`
+- **Install hint:** `pip install basedpyright`
+
+## Install
+
+- **macOS:** `pip install basedpyright` (or `uv tool install basedpyright`)
+- **Linux:** `pip install basedpyright` (or `uv tool install basedpyright`)
+- **Windows:** `pip install basedpyright`
+
+Prefer `uv tool install basedpyright` when the project uses uv — it keeps the
+server isolated from project venvs and always on PATH.
+
+Confirm it resolves:
+
+```bash
+command -v basedpyright-langserver
+```
+
+## Configure
+
+Add a `python` entry to the Hermes LSP config under `lsp.<language>`. Hermes keys
+each entry by language name with a `command` array and an `extensions` list:
+
+```json
+{
+  "lsp": {
+    "python": {
+      "command": [
+        "basedpyright-langserver",
+        "--stdio"
+      ],
+      "extensions": [
+        ".py",
+        ".pyi"
+      ]
+    }
+  }
+}
+```
+
+Hermes routes `.py`/`.pyi` edits to this server via the `extensions` list.
+Type-check strictness lives in `pyrightconfig.json` or `[tool.basedpyright]` in
+`pyproject.toml`, not in the Hermes LSP config.
+
+## Choosing a server
+
+Type checkers and the linter serve different roles. Run a type server, and
+optionally `ruff` ALONGSIDE it (not instead). Set the `command` accordingly:
+
+| command                              | install                | role                                    |
+| ------------------------------------ | ---------------------- | --------------------------------------- |
+| `["basedpyright-langserver", "--stdio"]` | `pip install basedpyright` | strictest types, **default**       |
+| `["pyright-langserver", "--stdio"]`  | `pip install pyright`  | upstream Microsoft type checker         |
+| `["ty", "server"]`                   | `pip install ty`       | Astral, very fast, pre-1.0/experimental |
+| `["ruff", "server"]`                 | `pip install ruff`     | lint + format only, complements a type server |
+
+Recommended: keep `basedpyright` as the `python` entry. `ruff` does not
+type-check, so if you want lint diagnostics too run it as a separate tool rather
+than replacing the type server.
+
+## Troubleshooting
+- **PATH:** `basedpyright-langserver` must be on PATH; reopen shell after install. `uv tool install` writes to `~/.local/bin`.
+- **Wrong interpreter / missing imports:** the server must see the project venv. Set `python.pythonPath` / `venvPath` in `pyrightconfig.json`, or activate the venv before launching.
+
+## Verify
+
+```bash
+node --experimental-strip-types ../../scripts/verify-lsp.ts path/to/file.py
+# or: bun ../../scripts/verify-lsp.ts path/to/file.py
+```

package/assets/lithermes-plugin/skills/lsp-setup/references/ruby/README.md

@@ -0,0 +1,67 @@
+# Ruby — LSP setup (Hermes / LitHermes)
+
+- **Recommended server:** `rubocop --lsp`
+- **Extensions:** `.rb .rake .gemspec .ru`
+- **Install hint:** `gem install rubocop`
+
+> **Note:** the executable invoked is **`rubocop`** (`rubocop --lsp`). RuboCop must be installed: `gem install rubocop`.
+
+## Install
+
+- **macOS:** `gem install rubocop`
+- **Linux:** `gem install rubocop`
+- **Windows:** `gem install rubocop`
+
+In a Bundler project, prefer adding `rubocop` to the `Gemfile` and running via `bundle exec`.
+
+Confirm it resolves (check `rubocop`, since that is what runs):
+
+```bash
+command -v rubocop
+```
+
+## Configure
+
+Add a `ruby` entry to the Hermes LSP config under `lsp.<language>`:
+
+```json
+{
+  "lsp": {
+    "ruby": {
+      "command": [
+        "rubocop",
+        "--lsp"
+      ],
+      "extensions": [
+        ".rb",
+        ".rake",
+        ".gemspec",
+        ".ru"
+      ]
+    }
+  }
+}
+```
+
+Hermes routes these extensions to `rubocop --lsp` via the `extensions` list. Behavior is
+driven by your `.rubocop.yml`; the server surfaces RuboCop diagnostics,
+formatting, and code actions over LSP.
+
+## Alternatives
+
+- **Shopify `ruby-lsp`** — the standalone `ruby-lsp` executable, richer navigation than RuboCop alone. Set the `command` to `["ruby-lsp"]`.
+- **`solargraph`** — older completion/type server; install with `gem install solargraph`, set the `command` to `["solargraph", "stdio"]`.
+
+## Troubleshooting
+
+- **PATH:** `rubocop` on PATH (that is the invoked binary); reopen shell after install.
+- **`rubocop` not found:** install RuboCop with `gem install rubocop`.
+- **Bundler mismatch:** if the project pins RuboCop in its `Gemfile`, run inside the bundle so versions match.
+- **No diagnostics:** check `.rubocop.yml` is valid and not disabling everything.
+
+## Verify
+
+```bash
+node --experimental-strip-types ../../scripts/verify-lsp.ts path/to/file.rb
+# or: bun ../../scripts/verify-lsp.ts path/to/file.rb
+```

package/assets/lithermes-plugin/skills/lsp-setup/references/rust/README.md

@@ -0,0 +1,65 @@
+# Rust — LSP setup (Hermes / LitHermes)
+
+- **Recommended server:** `rust-analyzer`
+- **Extensions:** `.rs`
+- **Install hint:** `rustup component add rust-analyzer`
+
+## Install
+
+- **macOS:** `rustup component add rust-analyzer` (or `brew install rust-analyzer`)
+- **Linux:** `rustup component add rust-analyzer`
+- **Windows:** `rustup component add rust-analyzer`
+
+The rustup component is the recommended path — it stays pinned to your toolchain.
+`rust-analyzer` also needs the `rust-src` component to index the standard library
+(`rustup component add rust-src`).
+
+Confirm it resolves:
+
+```bash
+command -v rust-analyzer
+```
+
+## Configure
+
+Add a `rust` entry to the Hermes LSP config under `lsp.<language>`:
+
+```json
+{
+  "lsp": {
+    "rust": {
+      "command": [
+        "rust-analyzer"
+      ],
+      "extensions": [
+        ".rs"
+      ]
+    }
+  }
+}
+```
+
+Hermes routes `.rs` edits to `rust-analyzer` via the `extensions` list. Options
+such as switching the check command to clippy live in `rust-analyzer` settings
+consumed by your editor, not in the Hermes LSP config.
+
+## Alternatives
+
+None — `rust-analyzer` is the official and sole Rust language server.
+
+## Troubleshooting
+- **PATH:** `rust-analyzer` must be on PATH; reopen shell after install. The rustup shim lives in `~/.cargo/bin`.
+- **Exits while loading rust-src:** if rust-analyzer crashes during stdlib indexing, reinstall the source component:
+
+  ```bash
+  rustup component remove rust-src && rustup component add rust-src
+  ```
+
+- **No proc-macro / build script support:** ensure the project builds with `cargo check`; rust-analyzer reuses the same toolchain.
+
+## Verify
+
+```bash
+node --experimental-strip-types ../../scripts/verify-lsp.ts path/to/file.rs
+# or: bun ../../scripts/verify-lsp.ts path/to/file.rs
+```

package/assets/lithermes-plugin/skills/lsp-setup/references/swift/README.md

@@ -0,0 +1,64 @@
+# Swift — LSP setup (Hermes / LitHermes)
+
+- **Recommended server:** `sourcekit-lsp`
+- **Extensions:** `.swift .objc .objcpp`
+- **Install hint:** `Included with Xcode or the Swift toolchain`
+
+## Install
+
+`sourcekit-lsp` ships with the Swift toolchain — no separate install.
+
+- **macOS:** `xcode-select --install` (or install full Xcode). It resolves to the active toolchain selected by `xcode-select`.
+- **Linux:** Install a swift.org toolchain (`sourcekit-lsp` ships inside it); add the toolchain's `usr/bin` to PATH.
+- **Windows:** Install the swift.org Windows toolchain; `sourcekit-lsp` is bundled.
+
+Confirm it resolves:
+
+```bash
+command -v sourcekit-lsp
+```
+
+## Configure
+
+Add a `swift` entry to the Hermes LSP config under `lsp.<language>`:
+
+```json
+{
+  "lsp": {
+    "swift": {
+      "command": [
+        "sourcekit-lsp"
+      ],
+      "extensions": [
+        ".swift",
+        ".objc",
+        ".objcpp"
+      ]
+    }
+  }
+}
+```
+
+Hermes routes these extensions to `sourcekit-lsp` via the `extensions` list. For best
+results the project needs a **SwiftPM `Package.swift`** or a
+`compile_commands.json` compilation database so the server can resolve modules.
+
+## Alternatives
+
+**No mainstream alternative.** `sourcekit-lsp` is the official Apple/swift.org
+server and the only practical choice.
+
+## Troubleshooting
+
+- **PATH:** `sourcekit-lsp` on PATH; reopen shell after install (or after `xcode-select -s`).
+- **Wrong toolchain (macOS):** point `xcode-select` at the right Xcode/toolchain; mismatches cause stale or missing results.
+- **No `Package.swift` / compile db:** add a SwiftPM manifest or generate `compile_commands.json` for accurate indexing.
+- **Objective-C (`.objc`/`.objcpp`):** needs a compilation database to resolve headers and frameworks.
+- **First build slow:** the server builds the module graph on first open; wait for it.
+
+## Verify
+
+```bash
+node --experimental-strip-types ../../scripts/verify-lsp.ts path/to/File.swift
+# or: bun ../../scripts/verify-lsp.ts path/to/File.swift
+```