Skip to main content
skill CX Codex

phoenix-liveview — Claude Code skill: Phoenix + LiveView on the BEAM

phoenix-liveview — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode that equips agents to build Phoenix and LiveView applications with OTP, Ecto, PubSub, and Presence.

MIT 438 installs ★ 80 updated 2026-07-18

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add bobmatnyc/claude-mpm-skills --skill phoenix-liveview -a claude-code
Open on GitHub

What phoenix-liveview does

The skill loads Phoenix and LiveView patterns directly into the agent's context across all six supported platforms. It covers OTP supervision trees, Ecto schemas with changesets, LiveView modules (mount, handle_event, render), live components, PubSub subscriptions, and multi-step transactions with Ecto.Multi.

Inside the skill file are ready-to-use Elixir snippets: GenServer for stateful services, pipeline routing in router.ex, assign_new/3 for lazy session-level computation, and stream/3 for large list diffs. The agent draws on these when generating code, so it can propose a concrete project structure — application.ex, contexts, router scopes — without several rounds of back-and-forth.

The skill is flagged disable-model-invocation: true and user-invocable: false, so there is no manual trigger command. The agent picks it up automatically when the conversation involves Phoenix or Elixir. Erlang and Elixir must be present in PATH; the skill points to asdf as the recommended version manager.

What it helps with

  • scaffold a Phoenix project with LiveView, Ecto, and esbuild in one command
  • build an OTP supervision tree with correct restart strategies
  • implement user registration via changeset and Ecto.Multi with email delivery
  • add a PubSub subscription in LiveView to broadcast updates to connected clients
  • split domain logic into contexts (Accounts, Billing) with clear boundaries

Example prompts for the agent

  • Create a LiveView counter with an increment button and server-side state
  • Write an Accounts context with registration through Ecto.Multi and Argon2 password hashing
  • Set up a PubSub subscription in mount/3 so the LiveView receives updates from other processes

How to install phoenix-liveview

1Skills CLI (Vercel)

npx skills add bobmatnyc/claude-mpm-skills --skill phoenix-liveview -a claude-code

2Manually: put the files in place

~/.claude/skills/phoenix-liveview/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/phoenix-liveview/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about phoenix-liveview

How do I install phoenix-liveview in Claude Code?

Run npx skills add bobmatnyc/claude-mpm-skills --skill phoenix-liveview -a claude-code. The skill file lands at ~/.claude/skills/phoenix-liveview/SKILL.md and the agent starts using it automatically.

What does the phoenix-liveview skill do?

It injects Phoenix and LiveView patterns into the agent's context: OTP supervision, Ecto contexts, LiveView modules, PubSub, and Presence. The agent uses these when generating code for BEAM-based web apps, skipping repeated clarification rounds.

Does the machine need anything installed for the skill to work?

Erlang and Elixir must be available in PATH. The skill points to asdf for version management. Without a working Elixir environment the agent can generate code but cannot run or test the project.

Source text

SKILL.md · MIT
---
name: phoenix-liveview
description: "Phoenix Framework with LiveView on the BEAM"
user-invocable: false
disable-model-invocation: true
version: 1.0.0
category: toolchain
author: Claude MPM Team
license: MIT
progressive_disclosure:
  entry_point:
    summary: "Phoenix + LiveView on the BEAM for fault-tolerant, real-time web apps (OTP, Ecto, PubSub, Presence)."
    when_to_use:
      - "Building real-time, resilient web apps with minimal client-side JS"
      - "Needing fault tolerance, supervision, and soft-realtime latency on the BEAM"
      - "Using Ecto + Phoenix contexts for clear domain boundaries"
      - "Delivering interactive UI via LiveView without a heavy SPA bundle"
    quick_start:
      - "Install Erlang/Elixir (asdf or brew); mix archive.install hex phx_new"
      - "mix phx.new my_app --live && cd my_app && mix deps.get"
      - "mix ecto.create && mix phx.server (visit http://localhost:4000)"
  token_estimate:
    entry: 180
    full: 5600
---

# Phoenix + LiveView (Elixir/BEAM)

Phoenix builds on Elixir and the BEAM VM to deliver fault-tolerant, real-time web applications with minimal JavaScript. LiveView keeps UI state on the server while streaming HTML diffs over WebSockets. The BEAM provides lightweight processes, supervision trees, hot code upgrades, and soft-realtime scheduling.

**Key ideas**
- OTP supervision keeps web, data, and background processes isolated and restartable.
- Contexts encode domain boundaries (e.g., Accounts, Billing) around Ecto schemas and queries.
- LiveView renders HTML on the server, syncing UI state over WebSockets with minimal client code.
- PubSub + Presence enable fan-out updates, tracking, and collaboration features.

---

## Environment and Project Setup

```bash
# Erlang + Elixir via asdf (recommended)
asdf install erlang 27.0
asdf install elixir 1.17.3
asdf global erlang 27.0 elixir 1.17.3

# Install Phoenix generator
mix archive.install hex phx_new

# Create project with LiveView + Ecto + esbuild
mix phx.new my_app --live
cd my_app
mix deps.get
mix ecto.create
mix phx.server
```

Project layout (key pieces):
- `lib/my_app/application.ex` — OTP supervision tree (Repo, Endpoint, Telemetry, PubSub, Oban, etc.)
- `lib/my_app_web/endpoint.ex` — Endpoint, plugs, sockets, LiveView config
- `lib/my_app_web/router.ex` — Pipelines, scopes, routes, LiveSessions
- `lib/my_app/` — Contexts (domain modules) and Ecto schemas
- `test/support/{conn_case,data_case}.ex` — Testing helpers for Ecto + Phoenix

---

## BEAM + OTP Essentials

**Supervision tree (application.ex)**: keep short, isolated children.
```elixir
def start(_type, _args) do
  children = [
    MyApp.Repo,
    {Phoenix.PubSub, name: MyApp.PubSub},
    MyAppWeb.Endpoint,
    {Oban, Application.fetch_env!(:my_app, Oban)},
    MyApp.Metrics
  ]

  Supervisor.start_link(children, strategy: :one_for_one, name: MyApp.Supervisor)
end
```

**GenServer pattern**: wrap stateful services.
```elixir
defmodule MyApp.Counter do
  use GenServer

  def start_link(initial \\ 0), do: GenServer.start_link(__MODULE__, initial, name: __MODULE__)
  def increment(), do: GenServer.call(__MODULE__, :inc)

  @impl true
  def handle_call(:inc, _from, state) do
    new_state = state + 1
    {:reply, new_state, new_state}
  end
end
```

**BEAM principles**
- Prefer many small processes; processes are cheap and isolated.
- Supervise everything with clear restart strategies.
- Use message passing (`GenServer.cast`/`send`) to avoid shared state.
- Use ETS/Cachex for in-memory caches; keep them supervised.

---

## Phoenix Anatomy and Routing

**Pipelines and scopes (router.ex)**: keep browser/api concerns separated.
```elixir
defmodule MyAppWeb.Router do
  use MyAppWeb, :router

  pipeline :browser do
    plug :accepts, ["html"]
    plug :fetch_session
    plug :fetch_live_flash
    plug :protect_from_forgery
    plug :put_secure_browser_headers
    plug :fetch_current_user
  end

  pipeline :api do
    plug :accepts, ["json"]
  end

  scope "/", MyAppWeb do
    pipe_through :browser
    live "/", HomeLive
    resources "/users", UserController
  end

  scope "/api", MyAppWeb do
    pipe_through :api
    resources "/users", Api.UserController, except: [:new, :edit]
  end
end
```

**Plugs**: composable request middleware. Keep plugs pure and short; prefer pipeline plugs over controller plugs when cross-cutting.

---

## Contexts and Ecto

**Schema + changeset**
```elixir
defmodule MyApp.Accounts.User do
  use Ecto.Schema
  import Ecto.Changeset

  schema "users" do
    field :email, :string
    field :hashed_password, :string
    field :confirmed_at, :naive_datetime
    timestamps()
  end

  def registration_changeset(user, attrs) do
    user
    |> cast(attrs, [:email, :password])
    |> validate_required([:email, :password])
    |> validate_format(:email, ~r/@/)
    |> validate_length(:password, min: 12)
    |> unique_constraint(:email)
    |> put_password_hash()
  end

  defp put_password_hash(%{valid?: true} = changeset),
    do: put_change(changeset, :hashed_password, Argon2.hash_pwd_salt(get_change(changeset, :password)))
  defp put_password_hash(changeset), do: changeset
end
```

**Context API**
```elixir
defmodule MyApp.Accounts do
  import Ecto.Query, warn: false
  alias MyApp.{Repo, Accounts.User}

  def list_users, do: Repo.all(User)
  def get_user!(id), do: Repo.get!(User, id)

  def register_user(attrs) do
    %User{}
    |> User.registration_changeset(attrs)
    |> Repo.insert()
  end
end
```

**Transactions with Ecto.Multi**
```elixir
alias Ecto.Multi

def register_and_welcome(attrs) do
  Multi.new()
  |> Multi.insert(:user, User.registration_changeset(%User{}, attrs))
  |> Multi.run(:welcome_email, fn _repo, %{user: user} ->
    MyApp.Mailer.deliver_welcome(user)
    {:ok, :sent}
  end)
  |> Repo.transaction()
end
```

---

## LiveView Patterns

**LiveView module (stateful UI on server)**
```elixir
defmodule MyAppWeb.CounterLive do
  use MyAppWeb, :live_view

  def mount(_params, _session, socket) do
    {:ok, assign(socket, count: 0)}
  end

  def handle_event("inc", _params, socket) do
    {:noreply, update(socket, :count, &(&1 + 1))}
  end

  def render(assigns) do
    ~H"""
    <div class="space-y-4">
      <p class="text-lg">Count: <%= @count %></p>
      <button phx-click="inc" class="btn">Increment</button>
    </div>
    """
  end
end
```

**HEEx tips**
- Prefer `assign_new/3` to lazily compute expensive data only once per connected session.
- Use `stream/3` for large lists to minimize diff payloads.
- Handle params in `handle_params/3` for URL-driven state; avoid storing socket state in params.

**Live Components**
```elixir
defmodule MyAppWeb.NavComponent do
  use MyAppWeb, :live_component
  def render(assigns) do
    ~H"""
    <nav>
      <%= for item <- @items do %>
        <.link navigate={item.href}><%= item.label %></.link>
      <% end %>
    </nav>
    """
  end
end
```

**PubSub-driven LiveView**
```elixir
@impl true
def mount(_params, _session, socket) do
  if connected?(socket), do: Phoenix.PubSub.subscribe(MyApp.PubSub, "orders")
  {:ok, assign(socket, orders: [])}
end

@impl true
def handle_info({:order_created, order}, socket) do
  {:noreply, update(socket, :orders, fn orders -> [order | orders] end)}
end
```

---

## PubSub, Channels, and Presence

**Broadcast changes from contexts**
```elixir
def create_order(attrs) do
  with {:ok, order} <- %Order{} |> Order.changeset(attrs) |> Repo.insert() do
    Phoenix.PubSub.broadcast(MyApp.PubSub, "orders", {:order_created, order})
    {:ok, order}
  end
end
```

**Presence for online/typing indicators**
```elixir
defmodule MyAppWeb.RoomChannel do
  use Phoenix.Channel
  alias Phoenix.Presence

  def join("room:" <> room_id, _payload, socket) do
    send(self(), :after_join)
    {:ok, assign(socket, :room_id, room_id)}
  end

  def handle_info(:after_join, socket) do
    Presence.track(socket, socket.assigns.user_id, %{online_at: System.system_time(:second)})
    push(socket, "presence_state", Presence.list(socket))
    {:noreply, socket}
  end
end
```

**Security**: authorize topics in `join/3`, verify user tokens in params/session, and limit payload size.

---

## Testing Phoenix + LiveView

Use `mix test` with the generated helpers.

```elixir
# test/support/conn_case.ex
use MyAppWeb.ConnCase, async: true

test "renders home", %{conn: conn} do
  conn = get(conn, "/")
  assert html_response(conn, 200) =~ "Welcome"
end
```

```elixir
# LiveView test
use MyAppWeb.ConnCase, async: true
import Phoenix.LiveViewTest

test "counter increments", %{conn: conn} do
  {:ok, view, _html} = live(conn, "/counter")
  view |> element("button", "Increment") |> render_click()
  assert render(view) =~ "Count: 1"
end
```

**DataCase**: provide sandboxed DB connections; wrap tests in transactions to isolate data.

**Fixtures**: build factories with `ExMachina` or simple helper modules under `test/support/fixtures`.

---

## Performance, Ops, and Deployment

- **Telemetry**: Phoenix exposes events (`[:phoenix, :endpoint, ...]`). Export via `:telemetry_poller`, `OpentelemetryPhoenix`, and `OpentelemetryEcto`.
- **Assets**: `mix assets.deploy` runs npm install, esbuild, tailwind (if configured), and digests.
- **Releases**: `MIX_ENV=prod mix release`. Configure runtime env in `config/runtime.exs`. Start with `PHX_SERVER=true _build/prod/rel/my_app/bin/my_app start`.
- **Clustering**: add `libcluster` with DNS/epmd strategy for horizontal scale; use distributed PubSub/Presence.
- **Caching**: use ETS/Cachex for hot paths; prefer short TTLs and invalidate on write.
- **Background jobs**: Oban for retries/backoff; supervise it in application tree.
- **Hot path checks**: enable `:telemetry` metrics, check LiveView diff sizes, avoid large assigns; prefer streams.

---

## Common Pitfalls

- Forgetting to subscribe LiveViews to PubSub after `connected?/1` check — events will be missed on initial render.
- Doing heavy work inside LiveView render; move to contexts and precompute assigns.
- Not using `Ecto.Multi` for multi-step writes; failures leave partial state.
- Blocking BEAM schedulers with long NIFs or heavy CPU work; offload to ports/Oban jobs.
- Overusing global ETS without supervision or limits; leak memory.

---

## Reference Commands

- `mix phx.routes` — list routes and LiveView paths.
- `mix phx.gen.live Accounts User users email:string confirmed_at:naive_datetime` — generate LiveView CRUD (review context boundaries afterward).
- `mix format && mix credo --strict` — formatting and linting.
- `mix test --seed 0 --max-failures 1` — deterministic failures; pair with `mix test.watch`.

Phoenix + LiveView excels when domain logic stays in contexts, LiveViews stay thin, and the BEAM supervises every component for resilience.

© Claude MPM Team · MIT · bobmatnyc/claude-mpm-skills

Similar skills

All skills for Backend and APIs →

From the same set143

The whole set →
hono-middleware A skill covering Hono middleware: writing your own, composing them, the built-in modules and the order they run in. Useful when a Hono app needs auth, CORS or logging. CX Codex +1 452installs golang-cli-cobra-viper golang-cli-cobra-viper — a skill for Claude Code, Codex, Cursor, and three other platforms that trains the agent to build multi-command Go CLIs with Cobra and Viper. Covers command structure, layered config, and shell completion generation. CX Codex +1 444installs wordpress-plugin-fundamentals wordpress-plugin-fundamentals — a skill for building WordPress plugins on PHP 8.3+ with OOP, hooks, database access and the Settings API. Useful when the agent has to scaffold a plugin instead of guessing at structure. CX Codex +1 440installs dependency-audit dependency-audit — a skill that walks through dependency cleanup: outdated packages, security vulnerabilities and libraries nothing imports anymore. CX Codex +1 439installs wordpress-testing-qa wordpress-testing-qa — a skill for testing WordPress plugins and themes: PHPUnit integration, WP_Mock, PHPCS and CI/CD. Useful when your test setup needs structure. CX Codex +1 436installs digitalocean-compute Tells your agent which DigitalOcean compute to use for a job: Droplets, App Platform, Functions, DOKS or GPUs. Handy when you are deciding where an app or container should run. CX Codex +1 435installs database-migration database-migration guides AI coding assistants through zero-downtime database schema updates. It provides safe multi-phase migration templates and rollback guides. CX Codex +1 432installs hono-testing hono-testing — a skill that shows how to test Hono apps: build a Request, hand it to the app, check the Response. Covers the typed test client and Workers bindings too. CX Codex +1 431installs

Project sponsors

Companies that keep this analytics open