Elixir and Phoenix Context for Claude Code, Codex, OpenCode and Pi

jamiecurle1 pts0 comments

phxagents<br>Skip to content<br>Search docs, skills… ⌘K Star 340 Install

v2.10.4 · stable for Claude Code

Elixir & Phoenix<br>context for Claude Code,<br>Codex, OpenCode & Pi.

A plugin that teaches your AI editor how Phoenix actually works — contexts, scopes, LiveView async patterns, Ecto.Multi, Oban idempotency, and the production safety rails (Iron Laws) that keep generated code from hurting you in prod.

Install in 30 seconds

Browse the catalog

45 skills 22 agents 22 Iron Laws · MIT licensed

~/my-phoenix-app · claude-code

›/phx:init<br>✓ Installing Iron Laws into CLAUDE.md<br>✓ Auto-activation rules registered<br>✓ 128 references auto-loaded<br>Ready. Try /phx:help<br>›/phx:plan add billing portal with Stripe checkout<br>→ phoenix-patterns-analyst: scanning lib/billing<br>→ ecto-schema-designer: drafting Subscription, Invoice schemas<br>→ security-analyzer: webhook signature, idempotency keys<br>→ oban-specialist: retry policy, dead-letter queue<br>✓ plan.md written · 14 steps · ~280 LOC est.<br>›/phx:work

67<br>Skills + Agents<br>1/4<br>AI clients · 3 in v3.0<br>22<br>Iron Laws enforced<br>v2.10.4<br>Latest · 3 days ago

Why phxagents Phoenix-shaped guardrails, not generic prompting.<br>Generic AI editors hallucinate Repo.preload in the wrong places, swallow exceptions with bare rescue, and skip Ecto.Multi for transactions. phxagents knows the patterns and refuses to ship code that breaks them.

Iron Laws enforced<br>22 non-negotiable rules: no Repo in loops, no bare rescues, no untyped Oban args, no missing preload. The judge agent blocks PRs that violate them.<br>iron-law-judge · /phx:review

Parallel review, 4 specialists<br>elixir-reviewer, security-analyzer, testing-reviewer and verification-runner each read the diff in fresh context, then findings are deduped and triaged. No more single-pass slop.<br>/phx:review

Compound docs<br>Every fixed bug is captured as a searchable solution doc with YAML frontmatter. Next time you hit a similar Ecto constraint error, the answer is one query away.<br>/phx:compound

Workflow, not autocomplete<br>/phx:plan → /phx:work → /phx:review → /phx:compound. Each step has compile, format and test gates. Generated code that doesn't pass mix test doesn't get committed.<br>/phx:full · end-to-end

Context-aware<br>Reads mix.exs to discover credo, dialyzer, sobelow, ex_check. Honors your custom aliases. Knows when you're on Phoenix 1.7 vs 1.8 Scope. Doesn't dictate — adapts.<br>verification-runner agent

Supply-chain aware<br>Audits Hex deps for bidi chars, compile-time exec, maintainer changes, typosquats and CVEs. Records vetted versions in hex_vet.exs so you don't re-review the same package twice.<br>/phx:deps-audit · /phx:deps-vet

The workflow Plan, work, review, compound.<br>One command per phase. Each phase produces an artifact the next phase reads. The cycle is the product.

Plan Specialist agents draft a multi-step plan.md with files, schemas and Oban jobs to touch.

/phx:plan<br>Work Implements step-by-step. mix compile and mix test verified after each step.

/phx:work<br>Review 4-track parallel review (Elixir, security, tests, verification) → findings → interactive triage.

/phx:review<br>Compound Captures what was learned as a searchable solution doc. Future you finds it in 2 seconds.

/phx:compound

Supported clients Shipping on Claude Code today. Three more in v3.0.<br>Claude Code is stable. Codex, OpenCode and Pi adapters land together in v3.0 with full Phase 1 + Phase 2 parity — single source, three generated targets. Track progress in PR #46.

C Claude Code<br>● stable v2.10.4

⌬ OpenAI Codex<br>v3.0 · in review PR #46

⌃ OpenCode<br>v3.0 · in review PR #46

π Pi<br>v3.0 · in review PR #46

Install in 30 seconds.<br>One plugin manifest in your .claude/ folder. Iron Laws and 45 skills auto-load.

Installation Browse catalog

esc

review code claude phoenix iron plan

Related Articles