Elixir / Phoenix — context-first agent sessions

Beam projects reward explicit module names and Mix task discipline. Akmon does not run mix for you unless you approve shell tool calls—so naming conventions in AKMON.md matter.

Prepare AKMON.md

Include:

  • Umbrella or single app layout (apps/ vs lib/).
  • Contexts that own domain logic (e.g. MyApp.Accounts).
  • Preferred checks: mix test, mix format, optional mix dialyzer.

Feature slice — LiveView or controller

akmon --plan --task "Plan a settings page restricted to admin users; list schemas, contexts, and tests to add"

Review .akmon/plans/ then:

akmon --yes --task "Implement the admin settings page per plan; add ExUnit tests for context functions"
mix test

Why plan mode helps

Phoenix moves through router → controller/live → context → schema. A plan file forces the agent to state that order before editing, which reduces half-written plugs or misnamed assigns.

Multi-agent note

You can run a cheap local model for --plan and a stronger cloud model for --yes on the same repo (Multi-agent & automation).

See Other languages for Elixir mentions in the generic profile path.