domains / families / software-engineering / elixir-pro

elixir-pro

combined

Write idiomatic Elixir code with OTP patterns, supervision trees, Write idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView. Masters concurrency, fault tolerance, and distributed systems.

When to use

• Working on elixir pro tasks or workflows
• Needing guidance, best practices, or checklists for elixir pro
• Implement or review Elixir/OTP supervision, process concurrency, Phoenix/Ecto boundaries, failure recovery and ExUnit coverage.

When not to use

• The task is unrelated to elixir pro
• You need a different domain or tool outside this scope
• This single-file guide is the available local procedure; no external reference pack or implementation-playbook is bundled or required. Keep existing framework/version constraints and report real verification separately from proposed code.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies share the same core Elixir/OTP/Phoenix focus, but the sickn33 copy adds material constraints and a different supervision stance that the rmyndharis copy lacks. The rmyndharis copy is a cleaner, more direct procedure, but crowning it would hide the sickn33 copy's explicit guidance on restart intensity, side-effect handling, and async test isolation, as well as its limitations section. Because the copies overlap but each has steps the others lack, and they disagree on the supervision philosophy, combine is the correct decision.