Elixir Phoenix Plugin for Claude Code
A Claude Code plugin for Elixir, Phoenix and LiveView: specialist agents, verification and rules against common mistakes
- 574 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Reads and edits project code
- Runs several agents and checks
- May connect Tidewave MCP
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/elixir-phoenix-plugin-for-claude-codeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads and edits project code
- Runs several agents and checks
- May connect Tidewave MCP
This is third-party code. Review the repository files before installing.
What it does
The plugin adds a set of specialist agents for the Elixir, Phoenix, LiveView, Ecto and Oban stack to Claude Code. They plan, implement, review and verify code in parallel, each with its own domain and fresh context. Separate rules, the Iron Laws, catch stack-specific bugs: assign_new silently skipping on reconnect, float corrupting money fields, non-idempotent Oban jobs. It includes planning, review and investigation commands and Tidewave MCP integration. Beyond Claude Code it ships editions for Amp, Codex, OpenCode and other environments.
Who it is for. For Elixir and Phoenix developers who write and review code through Claude Code.
Good fit when
- You want to plan a Phoenix or LiveView feature with parallel research
- You want a multi-agent review of Elixir code
- You want to catch typical Ecto, Oban and LiveView bugs before tests
Not a fit when
- The project is not on Elixir or Phoenix
- You need a general assistant not tied to one stack
Example request
Review this LiveView module and check the Oban jobs for idempotencyLimitations
The plugin targets the Elixir and Phoenix stack and needs a recent Claude Code; upgrading from older versions requires installing compatibility plugins in a strict order. Some features depend on Tidewave MCP, connected separately. Other environments (Amp, Codex, OpenCode, Pi, DeepSeek Harness) have separate editions with a reduced feature set.
How to disable. Remove the plugin via /plugin and drop the marketplace from the list in Claude Code.
FAQ
What are the Iron Laws?
A set of strict rules that describe the stack's danger zones and keep the agent from making Elixir and Phoenix specific mistakes.
Does it work outside Claude Code?
Yes, there are separate editions for Amp, Codex, OpenCode, Pi and DeepSeek Harness, but their feature sets differ.
Discussion
No questions or reviews yet.
Related
PluginsA plugin with 8 skills and 6 agents for Claude Code: Spring Boot 4, Java 21, JPA, tests and Kubernetes by one rule set.
Skills for Java projects: code review, Spring Boot, JPA, concurrency, Java version migration, Maven audits and security
A package records Phoenix LiveView sessions and replays them from assigns, with skills for agent setup and debugging.
The official Convex plugin for Cursor and Claude Code: rules, commands, MCP access and hooks for TypeScript backends.
Plinth
plinth
Skills and agents for Java development: build, tests, profiling and architecture. One-command installation for Claude Code, Cursor, Codex and Copilot
A Symfony plugin for Claude Code: 44 skills, 7 subagents and 13 commands for API Platform, Doctrine, TDD, Messenger and DDD
README in short
The README describes a Claude Code plugin that coordinates several specialist Elixir and Phoenix agents and applies the Iron Laws against common stack bugs. Installation adds a marketplace and runs a plugin install; commands appear as /phx:*, and upgrading from v2 has a strict order with ecto and lv compatibility plugins. Amp, Codex, OpenCode, Pi and DeepSeek Harness get separate editions with differing capabilities. It integrates with Tidewave MCP and documents everything on phxagents.dev. MIT licensed.