my-vue-rules

Domain-driven design in Phoenix contexts is enforced by standardizing boundary definitions, functional core patterns, and explicit naming conventions to maintain clear architectural separation and reduce drift.

Yes, you can use Credo and Dialyzer for Elixir code quality checks. This skill provides tooling recommendations that integrate Credo, Dialyzer, and ExUnit to enforce typing, testing, and performance conventions.

The best way to enforce type specs and documentation in Elixir is to apply standardized coding guidelines that require explicit naming, type specs, boundary enforcement, and consistent documentation across all modules.

Yes, this Elixir coding standardization suits large Phoenix applications. It applies to projects of varying sizes, guiding domain boundaries, testing conventions, and performance optimizations to maintain code quality at scale.

Phoenix architecture drifts as the codebase grows due to inconsistent coding practices and unenforced domain boundaries. Standardizing functional patterns, context boundaries, and tooling conventions reduces this drift and promotes maintainability.