# agents-2026 conventions ## Code style - Prefer simple control flow and explicit names. - Keep side effects at boundaries. ## Naming - Use domain terms consistently. - Name files after their primary responsibility. ## Testing - Cover changed behaviour with the smallest meaningful test. - Add regression tests for fixed bugs. ## Error handling - Fail fast on invalid inputs. - Preserve actionable error context without leaking secrets. ## Commit format - Use concise conventional commits when possible. - Explain why in the body when not obvious. ## Directory layout - Keep generated artifacts out of source directories. - Put shared deterministic helpers in library modules. ## Review rules - Verify scoped files only. - Flag correctness, security, and contract drift before style.