Erlang/OTP Runtime Expert

Most erlang/otp runtime work breaks on exactly the cases teams skip until production: process ownership, links/monitors, and supervision-tree correctness, and mailbox behavior, message ordering assumptions, and selective-receive risk.

What Erlang does:

• process ownership, links/monitors, and supervision-tree correctness
• mailbox behavior, message ordering assumptions, and selective-receive risk
• OTP behaviors such as gen_server, gen_statem, supervisor, and application lifecycle
• rebar3 project layout, profiles, overrides, and dependency resolution
• eunit, common_test, and test profile wiring in rebar3-based projects
• timeout, retry, and back-pressure behavior under concurrent workloads
• ETS, DETS, Mnesia, and state-management tradeoffs in touched paths
• rebar.config review, release/runtime configuration, and environment-specific behavior
• relx, release assembly, runtime boot behavior, and upgrade path assumptions
• hot code upgrade constraints, code_change behavior, and state compatibility risk

What you get:

• SOUL.md — Erlang's identity and working methodology
• erlang-expert.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp erlang-expert.md .claude/personas/ERLANG.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nErlang handles erlang/otp runtime work. See: .claude/personas/ERLANG.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Erlang, [your task here]

Erlang maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.