Claude Code Elixir
Install this marketplace when you ship Elixir or Phoenix backends in Claude Code and want LSP intelligence plus automatic compile, format, and Credo checks after every edit.
Overview
claude-code-elixir is a plugin marketplace for the Build phase that bundles Elixir LSP, Phoenix-oriented thinking skills, and Mix compile-format-Credo hooks for Claude Code.
What is this marketplace?
- Five plugins: elixir-lsp, elixir thinking skills, mix-compile, mix-format, and mix-credo
- Elixir LSP for go-to-definition, references, and hover documentation inside the agent
- Thinking skills covering Phoenix, Ecto, OTP, Oban, LiveView, and GenServer patterns
- Post-edit hooks run mix compile with warnings-as-errors, mix format, and Credo linting
- Tight feedback loop suited to solo builders iterating on Phoenix APIs and LiveView UIs
- Marketplace lists 5 plugins: elixir-lsp, elixir, mix-compile, mix-format, mix-credo
Community signal: 158 GitHub stars.
What problem does it solve?
Coding Elixir in Claude Code without LSP or automatic Mix checks means slow feedback, drift from team style, and warnings piling up until deploy day.
Who is it for?
Solo or small-team builders actively developing Phoenix, LiveView, or Oban-backed Elixir apps inside Claude Code.
Skip if: Teams on pure JavaScript stacks, non-Elixir backends, or agents that cannot run local Mix and LSP processes.
What do I get? / Deliverables
After you add the marketplace, edits trigger compile, format, and Credo hooks while skills and LSP keep Phoenix and OTP work accurate inside the same session.
- Five installable plugins covering LSP, domain skills, compile, format, and Credo
- Post-edit compile and lint feedback tied to the files you change
- Agent guidance aligned with Phoenix, Ecto, OTP, and Oban conventions
Plugins in this marketplace
5 plugins — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Elixir application work lives in the build phase; the bundle is cataloged on backend because Phoenix, Ecto, OTP, and Oban are core server-side concerns. Backend is the canonical shelf for language-server wiring, domain thinking skills, and Mix hook automation that keeps BEAM projects compiling cleanly.
How it compares
Language-specific Claude marketplace with LSP and hooks, not a generic MCP server or a single cross-stack skill.
Common Questions / FAQ
Who is Claude Code Elixir for?
It is for Elixir and Phoenix developers using Claude Code who want IDE-like LSP features and automatic Mix quality gates after each edit.
When should I use Claude Code Elixir?
Add it when you start or resume backend work on an Elixir codebase and want compile, format, and Credo enforced without manual terminal rituals.
How do I add Claude Code Elixir to my agent?
Register the georgeguimaraes/Claude Code Elixir marketplace in Claude Code, install the five listed plugins, and ensure Mix and the Elixir toolchain run on your machine.