my-xcx-rules

Elixir and Phoenix project structuring best practices enforce Domain-Driven Design and the Functional Core, Imperative Shell principle to keep business logic pure and boundaries well-defined, unifying module organization, API separation, and naming conventions across teams.

Apply functional core and imperative shell patterns in Phoenix by separating pure business logic from side-effect heavy boundary layers, ensuring explicit input validation, clear API/implementation separation, and well-documented architectural trade-offs for maintainers.

Yes, Elixir code audits require typespecs and documented public APIs to ensure consistent quality, as documenting public APIs, typespecs, naming conventions, and trade-offs guides maintainers and enforces coding patterns across teams.

The best way to enforce domain boundaries in Elixir applications is adopting Domain-Driven Design guidelines, enforcing clear module organization, pattern selection, and API design across contexts to keep boundaries well-defined and maintain consistent quality.

Yes, you can use these Elixir coding pattern rules for cross-team project audits, aligning architecture, pattern usage, and code quality across teams by enforcing guidelines for testing strategies, input validation, and style.