nerves_view

Elixir implementation — decision tables, templates, anti-patterns for idiomatic code. ALWAYS use when writing Elixir code, choosing control-flow constructs, writing OTP callbacks, writing tests/TDD, or refactoring toward idiomatic form.

Elixir architectural planning — the decisions made BEFORE writing code. Covers project layout, domain boundaries (contexts, aggregates), data ownership, multi-tenancy, process architecture and supervision, inter-context communication (direct call, PubSub, Registry, GenStage, Broadway, Oban, event sourcing), configuration, resilience (bulkheads, circuit breakers, retries, timeouts), architectural styles (hexagonal, modular monolith, CQRS, event-driven), growing from small to large, distributed systems, and anti-patterns. ALWAYS use when designing, architecting, structuring, or planning an Elixir application. ALWAYS use when choosing between umbrella/single-app, contexts, process placement, or supervision strategy. ALWAYS use when starting a new Elixir project or major refactor. For writing the code itself, also load elixir-implementing.

Code review, debugging, and profiling for Elixir. ALWAYS use when reviewing PRs, debugging issues, or profiling performance. For writing code → load implementing.