What problem does it solve? Codebases degrade over time through unclear naming, oversized methods, hidden side effects, duplication, and untested changes. This Skill gives an AI coding assistant a mandatory, language-agnostic engineering contract so every piece of code it writes, changes, or reviews meets consistent readability, testability, and maintainability standards. ## Core Features & Use Cases - Sixteen enforceable rules: Covers naming, small focused methods, abstraction-level separation, explicit side effects, guard clauses, error handling as design, cohesion, duplication removal, test-first development, and continuous refactoring. - Test-driven workflow: Requires a failing test before behavior changes or bug fixes, with regression coverage and readable, deterministic tests named by expected outcome. - Ecosystem-specific guidance: Includes detailed rules for Ecto queries (prefer assoc joins, recursive CTEs over N+1 Elixir recursion, Ecto DSL over raw SQL), Operately API enum/serializer modeling, and the Operately.Repo.Getter requester-aware loading pattern. - Use Case: Ask the assistant to refactor a tangled Elixir context module; it will extract intention-revealing functions, replace manual joins with assoc, convert per-step hierarchy queries into a recursive CTE, and add failing tests first. ## Quick Start Ask the assistant to refactor the attached module following clean-code principles and add tests for the changed behavior.
