From 38ebe5bdfa25775cefddd69eb94658bb423f4584 Mon Sep 17 00:00:00 2001 From: David Kaya Date: Tue, 24 Mar 2026 21:23:48 +0100 Subject: [PATCH] docs: revert agent things --- AGENTS.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 4f904bb..b5d39b3 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -34,9 +34,6 @@ These instructions apply to any automated or semi-automated agent working in thi - Avoid duplication when a shared abstraction improves clarity and maintainability. - Prefer composition and small reusable units over sprawling functions, deep inheritance, or tightly coupled code. - Make invalid states difficult to represent through types, structure, or APIs whenever the technology supports it. -- When refactoring, actively remove code smells instead of relocating them. Large multi-responsibility files, long methods, scattered mutable state, duplicated logic, and protocol or reflection glue mixed into orchestration code should usually be split into focused collaborators. -- Keep coordinator and orchestration types thin. Push policy decisions, parsing or translation, projection or mapping, and mutable execution state into dedicated helpers or services with clear ownership. -- For deep refactors, add characterization tests around the current behavior before extracting logic, then keep the tests aligned with the new collaborators so structure improves without changing behavior accidentally. - Add comments only when they explain intent, reasoning, or non-obvious behavior that the code itself cannot communicate clearly. ## 4. Core delivery standards