elixir-antipatterns

Common Elixir anti-patterns include improper error handling with tagged tuples, poor context separation, unoptimized Ecto queries, and weak testing practices. Identifying these flaws during code reviews reduces the risk of brittle Elixir/Phoenix applications and improves overall code quality.

Fix Ecto query anti-patterns during Phoenix project refactoring by applying codified patterns that optimize database interactions. The skill provides concrete code examples and architecture visuals to guide query remediation and enforce best practices for robust application design.

You need tagged tuples for error handling in Elixir when returning operation results to ensure robust pattern matching and prevent silent failures. Codifying this core anti-pattern enforces consistent error handling, reducing brittle application behavior during complex processing.

Yes, it covers advanced Elixir and Phoenix architecture patterns through extended reference materials. The skill enforces eight core anti-patterns and links to extended documentation covering over 40 patterns and advanced techniques for deeper architectural guidance.

The best way to improve Phoenix context separation is by identifying and remediating boundary anti-patterns using provided architecture visuals and concrete code examples. This enforces proper module boundaries and reduces coupling during refactoring sessions.

Yes, you can use this skill to enforce testing best practices for Elixir code. It explicitly catalogs testing anti-patterns as one of its eight core patterns, providing guidance to recognize and remediate common testing flaws during code reviews.