Claude Code Elixir
Claude Code plugins for Elixir development.
Installation
claude plugin marketplace add georgeguimaraes/claude-code-elixir
Install all plugins:
claude plugin install elixir-lsp@claude-code-elixir && \
claude plugin install mix-format@claude-code-elixir && \
claude plugin install mix-compile@claude-code-elixir && \
claude plugin install mix-credo@claude-code-elixir && \
claude plugin install elixir@claude-code-elixir
Prerequisites
Install the expert binary and make sure it's on your PATH. See installation instructions.
Note: mix-format, mix-compile, and mix-credo require bash (Git Bash or WSL on Windows).
Plugins
Overview
| Plugin | Type | Description |
|---|
| elixir-lsp | LSP | Language Server with completions, go-to-definition, diagnostics |
| mix-format | Hook | Auto-format .ex/.exs files on save |
| mix-compile | Hook | Compile with --warnings-as-errors on save |
| mix-credo | Hook | Run Credo code quality checks on save |
| elixir | Skills | BEAM architecture, Phoenix, Ecto, OTP patterns |
Tools
elixir-lsp
Elixir Language Server integration powered by Expert.
| Feature | Description |
|---|
| Navigation | Go to definition, find references |
| Completions | With signature help and docs |
| Diagnostics | Compiler warnings and errors |
| File types | .ex, .exs, .heex, .leex |
mix-format
Auto-runs mix format after editing .ex and .exs files.
mix-compile
Auto-runs mix compile --warnings-as-errors after editing .ex files.
- Only
.ex files (not .exs scripts/tests)
- Finds
mix.exs by walking up directories
- Fails on warnings or errors
mix-credo
Auto-runs mix credo after editing .ex and .exs files to check code quality.
- Runs on both
.ex and .exs files
- Uses project's default Credo configuration
- Gracefully skips if Credo is not installed
- Fails on code quality issues
Skills
elixir
Paradigm-shifting skills for Elixir, Phoenix, and OTP development. Includes a SessionStart hook that auto-suggests skills when working on Elixir code.
Included skills:
| Skill | Use When |
|---|
elixir-thinking | Designing modules, processes, data structures |
phoenix-thinking | Working with Phoenix, LiveView, PubSub |
ecto-thinking | Working with Ecto, contexts, schemas |
otp-thinking | Implementing GenServers, supervisors, Tasks |
elixir-thinking
Mental models for writing Elixir — how it differs from OOP.
| Concept | Insight |
|---|
| Iron Law | NO PROCESS WITHOUT A RUNTIME REASON |
| Three dimensions | Behavior, state, mutability are decoupled |
| Processes | For runtime (state/concurrency/faults), not code organization |
| "Let it crash" | Means "let it heal" — supervisors restart |
| Polymorphism | Behaviors → Protocols → Message passing (least to most dynamic) |
Sources
phoenix-thinking
Architectural patterns for Phoenix and LiveView.
| Concept | Insight |
|---|
| Iron Law | NO DATABASE QUERIES IN MOUNT |
| Scopes (1.8+) | Security-first authorization threading |
| mount vs handle_params | mount = setup, handle_params = data |
| PubSub | Scoped topics, broadcast_from to avoid self-broadcast |
| Channel fastlane | Socket state can be stale — re-fetch or include in broadcast |
Sources
ecto-thinking
Architectural patterns for Ecto and contexts.
| Concept | Insight |
|---|
| Contexts | Bounded domains with their own "dialect" |
| Cross-context refs | Use IDs, not belongs_to associations |
| Schemas | Multiple changesets per schema, embedded_schema for forms |
| Preloads | Separate vs join — pick based on data shape |
| pool_count vs pool_size | pool_count = DBConnection pools, pool_size = connections per pool |
Sources
