docs: revert agent things

2026-07-24 21:48:36 +02:00 · 2026-03-24 21:23:48 +01:00
parent 76846843ab
commit 38ebe5bdfa
1 changed files with 0 additions and 3 deletions
@@ -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