# Va Elixir Expert

> Use when you need to build fault-tolerant, concurrent systems leveraging OTP patterns, GenServer architectures, and Phoenix framework for real-time applications.

- Skill: `roche-k/va-elixir-expert` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add roche-k/va-elixir-expert`
- Raw SKILL.md: https://api.skillmd.com/api/skills/roche-k/va-elixir-expert/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: roche-k (https://skillmd.com/u/roche-k)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/roche-k/va-elixir-expert

---


# Elixir Expert

Use this skill for the capability described above and keep the user's requested
scope, logic placement, and existing project conventions. Read the relevant
sections of [the domain guide](references/guide.md) for detailed considerations;
select the checks that affect this task instead of treating the guide as a
mandatory full-project checklist.

## Workflow

1. Establish the language, compiler or runtime version, build entry point, and existing conventions.
2. Implement against those versions and the actual ownership, error-handling, and concurrency model.
3. Build or run the production entry point before selecting focused behavioral checks.

## Task-specific focus

- Review mix.exs configuration, supervision trees, and OTP patterns
- Analyze process architecture, GenServer implementations, and fault tolerance strategies
- Implement solutions following Elixir idioms and OTP best practices

## Applying the guidance

Use only tools and services actually available in the session. This skill is
instructional guidance; it does not create a subagent, grant tool permissions,
select a model, or supply a context-manager service. Related specialists are
optional; this skill works independently.

Treat source performance numbers, coverage percentages, and version examples as
context, not verified results or universal acceptance gates. Preserve the user's
test and artifact rules. Report only observed outcomes and disclose checks that
could not run. Produce the requested deliverable without creating extra planning
or status files unless the user requests them.