feat: add Claude Code marketplace and dexter-lsp plugin

.claude-plugin/marketplace.json

@@ -0,0 +1,14 @@
+{
+  "name": "dexter",
+  "owner": {
+    "name": "remoteoss",
+    "url": "https://github.com/remoteoss"
+  },
+  "plugins": [
+    {
+      "name": "dexter-lsp",
+      "source": "./plugins/dexter-lsp",
+      "description": "Dexter language server for Elixir (.ex, .exs, .heex)"
+    }
+  ]
+}

README.md

@@ -15,6 +15,7 @@ A fast, full-featured Elixir LSP optimized for large Elixir codebases.
     - [Configuring format on save](#configuring-format-on-save)
   - [Neovim (with nvim-lspconfig — \< 0.11)](#neovim-with-nvim-lspconfig---011)
   - [Zed](#zed)
+  - [Claude Code](#claude-code)
   - [Emacs](#emacs)
     - [Eglot](#eglot)
       - [Emacs version \>= 30](#emacs-version--30)
@@ -319,6 +320,29 @@ name = "elixir"
 language-servers = ["dexter"]
 ```
 
+### Claude Code
+
+[Claude Code](https://claude.ai/code) supports Dexter as an Elixir LSP via its plugin system, enabling go-to-definition, hover docs, find references, and more when working on `.ex`, `.exs`, and `.heex` files.
+
+**Prerequisites:** The LSP tool must be enabled. Add this to your `~/.claude/settings.json`:
+
+```json
+{
+  "env": {
+    "ENABLE_LSP_TOOL": "1"
+  }
+}
+```
+
+**Install:**
+
+```sh
+claude plugin marketplace add remoteoss/dexter
+claude plugin install dexter-lsp@dexter
+```
+
+That's it. Open an Elixir project in Claude Code and Dexter will handle go-to-definition, hover documentation, find references, and more.
+
 ## Why build another LSP?
 
 Remote has one of the largest Elixir codebases in existence (at least that we're aware of), now around 57k files. As our codebase has grown, we've had more and more struggles with language servers. We had found that they simply couldn't keep up with such a large codebase. On large codebases like ours, existing LSPs take hours to index, and even after indexing, operations like go-to-definition and go-to-references are still slow. On top of that, changing branches means a whole new round of indexing. The result has been frustration. Many of us on the engineering team had all but given up on the idea of ever having a working LSP.

plugins/dexter-lsp/.claude-plugin/plugin.json

@@ -0,0 +1,43 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
+  "name": "dexter-lsp",
+  "description": "Dexter language server for Elixir (.ex, .exs, .heex)",
+  "version": "0.1.0",
+  "author": {
+    "name": "remoteoss",
+    "url": "https://github.com/remoteoss"
+  },
+  "homepage": "https://github.com/remoteoss/dexter",
+  "repository": "https://github.com/remoteoss/dexter",
+  "license": "MIT",
+  "keywords": ["elixir", "lsp", "dexter", "phoenix", "heex"],
+  "lspServers": {
+    "dexter": {
+      "command": "dexter",
+      "args": ["lsp"],
+      "extensionToLanguage": {
+        ".ex": "elixir",
+        ".exs": "elixir",
+        ".heex": "phoenix-heex"
+      },
+      "initializationOptions": {
+        "followDelegates": "${user_config.follow_delegates}",
+        "debug": "${user_config.debug}"
+      }
+    }
+  },
+  "userConfig": {
+    "follow_delegates": {
+      "type": "boolean",
+      "title": "Follow delegates",
+      "description": "Jump through defdelegate to the target function definition",
+      "default": true
+    },
+    "debug": {
+      "type": "boolean",
+      "title": "Debug logging",
+      "description": "Enable verbose LSP logging to stderr",
+      "default": false
+    }
+  }
+}