Elm Review

Rules are written in Elm, leveraging the language's type safety and familiar syntax, as demonstrated in the custom rule example using `elm-syntax` for AST traversal.

Rules are shared as Elm packages, enabling a growing collection of static analyses that teams can adopt and contribute to, mentioned in the package registry search guidance.

Supports temporary suppression of errors with JSON files, allowing incremental adoption of rules without permanent disables, detailed in the suppression system documentation.

Facilitates custom rules for architectural decisions like centralizing image paths or mandating shared components, exemplified in the README's use cases.

Emphasizes well-designed rules over easily ignorable warnings and encourages API improvements first, reducing noise and ensuring meaningful analysis, as outlined in the 'When to write or enable a rule' section.