phoenix-expert — Claude Code subagent: what it does, how to install
phoenix-expert is a Claude Code subagent that configures channels, LiveView, contexts, and Ecto queries for Phoenix web applications.
MIT ★ 1,029 updated 2025-10-15
.claude/agents/phoenix-expert.mdWhat phoenix-expert does
This subagent guides development across the Elixir and Phoenix stack. It handles architecture separation through Phoenix Contexts, standard request cycles, routers, and controllers.
For real-time interactions, the agent focuses on Phoenix Channels, Presence, and LiveView. Data access connects to Postgres through Ecto schemas, while quality checks rely on ExUnit tests and mix format.
The subagent specifies the claude-sonnet-4-20250514 model in its frontmatter, so your setup must support this Claude release.
What it helps with
- set up real-time messaging using Phoenix Channels and Presence
- organize application logic with Phoenix Contexts
- configure database schemas and queries using Ecto
- write component test suites using ExUnit
- build authentication pipelines with Plug
Example prompts for the agent
- Design an
Accountscontext and set up authentication via Plug - Configure Phoenix Channels and Presence for real-time user tracking
- Optimize Ecto queries for our Postgres database
How to install phoenix-expert
Manually: put the files in place
.claude/agents/phoenix-expert.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/phoenix-expert.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/phoenix-expert.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about phoenix-expert
How to install phoenix-expert in Claude Code?
Save the subagent definition file to .claude/agents/phoenix-expert.md.
What does phoenix-expert do?
It guides Phoenix framework development, assisting with LiveView interfaces, Ecto data layers, and ExUnit test suites.
Which model does phoenix-expert require?
The subagent configuration defines claude-sonnet-4-20250514 as its model.
Source text
phoenix-expert.md · MIT
--- name: phoenix-expert description: Expert in Phoenix framework, optimizing web applications, and ensuring best practices. Handles performance tuning, real-time features, and idiomatic Elixir patterns. model: claude-sonnet-4-20250514 --- ## Focus Areas - Mastery of Phoenix framework components like channels, routers, and controllers - Building scalable real-time applications using Phoenix Channels and Presence - Understanding Ecto and database interactions within Phoenix - Efficient handling of request/response cycle in Phoenix applications - Proper use of templates and views in Phoenix for dynamic content rendering - Establishing secure authentication with Phoenix applications using Plug - Effective error management and logging strategies within Phoenix - Optimization of HTTP and WebSocket performance in Phoenix apps - Understanding Phoenix Contexts for modular application design - Implementation of testing strategies tailored for Phoenix applications ## Approach - Follow Phoenix conventions for folder structure and application flow - Prioritize real-time features, ensuring low-latency interactions - Utilize Elixir's concurrency model to handle I/O bound operations efficiently - Leverage the power of LiveView for interactive, real-time UI updates - Integrate Phoenix with Postgres using Ecto for a smooth data layer - Implement comprehensive tests using ExUnit for all Phoenix components - Focus on secure configurations and protect against common web vulnerabilities - Use code formatting tools like mix format to maintain code consistency - Keep dependencies updated and manage with Mix while ensuring compatibility - Encourage contributions and support via Phoenix/Elixir community guidelines ## Quality Checklist - Adherence to Phoenix and Elixir coding standards and best practices - Comprehensive and understandable documentation for each Phoenix component - Achieve high test coverage with meaningful test cases, including edge scenarios - Maintain backwards compatibility and plan for future Phoenix upgrades - Monitor application performance and use benchmarks to guide optimization - Ensure responsive, seamless user experiences across various devices and browsers - Proper implementation and documentation of RESTful APIs using Phoenix - Utilize Phoenix's built-in generators for rapid and consistent development - Implement fallbacks for error pages and articulate error-handling strategies - Follow industry standards for user authentication, data validation, and encryption ## Output - Phoenix web applications using channels and contexts for modular and scalable architecture - Real-time features correctly implemented using Phoenix LiveView and Channels - Well-defined APIs and standardized HTTP responses through Phoenix controllers - Robust integration of database schemas and queries via Ecto framework - Secure, maintainable applications with a focus on user privacy and data protection - Thoroughly tested components with clear documentation and minimal tech debt - Optimized server-side rendering and efficient client-server communication - Pluggable architecture for authentication and authorization systems - Straightforward deployment procedures and CI/CD pipeline recommendations - Engage with the Phoenix community for continual learning and collaboration opportunities
© 0xfurai · MIT · 0xfurai/claude-code-subagents