elixir-genius

Design Elixir/Phoenix/LiveView architectures with OTP supervision trees and ADRs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nxy7/streampai-elixir --skill elixir-genius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elixir-genius
Source: https://github.com/nxy7/streampai-elixir/tree/main/.claude/skills/elixir-genius
Command: npx skills add https://github.com/nxy7/streampai-elixir --skill elixir-genius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams design scalable, production-ready Elixir/Phoenix/LiveView architectures and generate comprehensive documentation packages.

Core Features & Use Cases

  • Architecture templates for Elixir/Phoenix/LiveView projects
  • OTP supervision tree planning and domain modeling
  • ADR-driven architecture decisions and handoff documentation
  • Real-world scenario handling such as multi-context systems and live view orchestration

Quick Start

Draft a complete architecture plan for a new Phoenix/LiveView application, including module boundaries, supervision tree, data models, and ADRs.

Frequently Asked Questions about elixir-genius

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a scalable Phoenix LiveView architecture for a new project?

To design a scalable Phoenix LiveView architecture, you need structured module boundaries, OTP supervision tree planning, and domain modeling. This Skill generates a complete architecture plan with concrete data models and ADRs to guide production-ready Elixir system development.

What is the best way to plan an OTP supervision tree for Elixir applications?

Planning an OTP supervision tree requires defining domain models and lifecycle guidance for Elixir applications. This Skill encodes architecture decisions into a repeatable structure, helping you map out supervision trees and handle real-world scenarios like multi-context systems.

How do I generate ADR-driven architecture documentation for Elixir systems?

Generating ADR-driven architecture documentation involves encoding architecture decisions and lifecycle guidance into a repeatable structure. This Skill produces ADRs and handoff documentation suitable for Director/Implementor AI workflows, ensuring production-ready Elixir system handoffs.

Can I use this to handle multi-context systems and live view orchestration?

Yes, handling multi-context systems and live view orchestration is a core feature. This Skill provides architecture templates and real-world scenario guidance for Elixir/Phoenix/LiveView projects, ensuring scalable and coordinated live view orchestration.

Do I need handoff documentation for Director/Implementor AI workflows in Elixir?

Handoff documentation is essential for Director/Implementor AI workflows to understand Elixir architecture decisions. This Skill creates comprehensive documentation packages containing ADRs, module boundaries, and data model references formatted for repeatable AI-driven implementation.

What are the limitations of using generic architecture templates for Elixir systems?

Generic architecture templates often lack specific OTP supervision tree planning and Phoenix LiveView orchestration guidance. This Skill overcomes limitations by encoding concrete data models, lifecycle guidance, and ADR-driven decisions tailored specifically for scalable Elixir production environments.