elixir-architecture

Document Elixir bounded contexts and public APIs for modular architecture.

Updated Jan 15, 2026

Search Tags:#architecture #elixir #architecture-patterns #modular #system-design #contexts #umbrella

Ready to run

npx skills add https://github.com/vircung/opencode-config --skill elixir-architecture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: elixir-architecture
Source: https://github.com/vircung/opencode-config/tree/main/skill/elixir-architecture
Command: npx skills add https://github.com/vircung/opencode-config --skill elixir-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Elixir system design patterns guide how to structure domains, contexts, and scalable architecture for distributed applications.

Core Features & Use Cases

Context-driven design: define bounded contexts as public APIs for business logic.
Context boundaries: avoid cross-context schema access and expose clean APIs.
System architecture patterns: guidance on typical Elixir app structures and umbrella setups, with practical examples.

Quick Start

Outline the top-level contexts for your Elixir app and sketch how they interact.

Frequently Asked Questions about elixir-architecture

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

FAQPage Schema

How do I structure bounded contexts in Elixir to build scalable systems?▼

Elixir bounded contexts structure domains by defining public APIs for business logic, preventing cross-context schema access to build scalable, maintainable applications. This enforces clear module organization and strict context boundaries.

What is the best way to organize Elixir contexts and avoid cross-context schema access?▼

Organizing Elixir contexts requires exposing clean public APIs and enforcing strict boundaries to avoid cross-context schema access. This modular architecture approach ensures maintainable system design across distributed services.

When do I need modular architecture patterns for distributed Elixir projects?▼

Modular architecture patterns are needed for distributed Elixir projects when you must define clear boundaries and public APIs across multiple services. This approach guides how to structure domains and contexts for scalable applications.

Does this Elixir architecture guidance cover umbrella setups and multi-service designs?▼

Yes, Elixir architecture guidance covers umbrella setups and multi-service designs by providing practical examples of typical application structures. It helps define how top-level contexts interact within distributed Elixir environments.

How do I document public APIs for Elixir bounded contexts?▼

Document public APIs for Elixir bounded contexts using a structured frontmatter and explanatory body to enforce design principles. This ensures clear module organization and defines clean APIs for business logic.

What are the limitations of using umbrella apps for Elixir system design?▼

Umbrella apps in Elixir system design require careful boundary management to prevent cross-context schema access and maintain clean public APIs. Clear module organization is enforced to mitigate complexity in distributed applications.