elixir-ecosystem

Use this agent for pure Elixir projects WITHOUT Phoenix/web UI — libraries, CLI tools, OTP applications, and backend services. For Phoenix web apps with LiveView/HEEx/UI, use elixir-phoenix-craftsperson instead. **When to use this agent:** - Elixir libraries and packages (hex packages) - CLI tools built with Elixir - OTP applications without web interfaces - Backend-only services (APIs without Phoenix, or Phoenix API-only) - Nerves/embedded Elixir projects - Pure business logic modules **Proactive Usage Examples:** - user: "I'm building a new Elixir library for parsing CSV files" assistant: "I'll use the elixir-craftsperson agent to implement this library with proper testing and documentation." - user: "I need to refactor this GenServer for better fault tolerance" assistant: "Let me use the elixir-craftsperson agent to review the OTP patterns and improve supervision." - user: "Review my Elixir package before publishing to Hex" assistant: "I'll use the elixir-craftsperson agent to audit code quality, security, and documentation." **Specific Scenarios:** - Implementing OTP patterns (GenServers, Supervisors, Tasks) - Building Elixir libraries with proper behaviours and protocols - Setting up test suites with Mox for external dependencies - Reviewing code for Credo violations and formatting - Running security audits with mix_audit and Sobelow - Creating pure functional cores with imperative shells - Designing mockable gateways for I/O operations **NOT for:** Phoenix LiveView, HEEx templates, web UI, dark mode, frontend concerns → use elixir-phoenix-craftsperson

Use this agent for Phoenix web applications with LiveView, HEEx templates, and UI/UX concerns. Includes full Elixir expertise PLUS Phoenix framework patterns, dark mode, and frontend polish. For pure Elixir without Phoenix UI, use elixir-craftsperson instead. **When to use this agent:** - Phoenix LiveView applications - Any work involving HEEx templates - Phoenix web apps with user interfaces - UI/UX implementation and review - Dark mode / theming / daisyUI styling - Full-stack Phoenix projects - Phoenix contexts that serve LiveViews **Proactive Usage Examples:** - user: "I've added a new LiveView for user settings" assistant: "Let me use the elixir-phoenix-craftsperson agent to review the LiveView patterns and verify dark mode compatibility." - user: "The form isn't displaying correctly" assistant: "I'll use the elixir-phoenix-craftsperson agent to debug the HEEx template and form handling." - user: "I need to add a modal with proper styling" assistant: "Let me use the elixir-phoenix-craftsperson agent to implement this with daisyUI theme-aware colors." - user: "Review my Phoenix app before deployment" assistant: "I'll use the elixir-phoenix-craftsperson agent to audit code quality, security, UI consistency, and dark mode." **Specific Scenarios:** - Building Phoenix LiveView interfaces - HEEx template syntax and patterns - Phoenix router, contexts, and Ecto schemas - Form handling with to_form/2 and changesets - LiveView streams, hooks, and JS interop - Dark mode with daisyUI theme-aware colors - Tailwind CSS v4 styling - Phoenix 1.8 patterns (Layouts, core_components) - Testing LiveViews with Phoenix.LiveViewTest **Also includes:** All pure Elixir patterns (OTP, testing, Credo, security audits)