From 1027d553f7df5b03aec39da23a427d1f3a9acaef Mon Sep 17 00:00:00 2001 From: mwiegand Date: Fri, 9 Oct 2026 22:50:29 +0200 Subject: [PATCH] docs(agents): code health rules move to the coding skill Co-Authored-By: Claude Mythos 5.1 Claude-Session: https://claude.ai/code/session_01UH8jPP1zXteddiR9pEd4KE --- agents/AGENTS.md | 24 +++--------------------- 1 file changed, 3 insertions(+), 21 deletions(-) diff --git a/agents/AGENTS.md b/agents/AGENTS.md index fa9b8e9..249bf7d 100644 --- a/agents/AGENTS.md +++ b/agents/AGENTS.md @@ -85,27 +85,9 @@ loop or brute-force through API calls. ## Code health -Strategic over tactical, with follow-through. Each change should leave the -codebase at least as coherent as it was — don't just *flag* messiness, address it. - -- **Default to acting on cleanups, not just mentioning them.** If you notice - duplication, a band-aid, or an inconsistency, fix it as part of the work - rather than leaving it as an observation. "I noticed X but didn't do it" - is the anti-pattern — it leaves the user with both the mess *and* the - homework of cleaning it up. -- **Scope boundary for inline cleanups: on-path AND reversible AND within - files already being touched.** Inline when all three hold. If the cleanup - crosses files, would be hard to undo, or is parallel to the task — - surface it in 2-3 sentences and ask before pursuing. -- **Tolerate duplication until the pattern is real.** Removing existing - duplication is welcome; inventing new abstractions speculatively is not. - Rule of three: don't unify two instances, wait for the third. -- **Treat friction as architectural data.** Awkward expression, edits that - ripple across files, patterns that recur with subtle variations, structure - fighting the task — these are the architecture telling you something, not - just noise to push through. Propose architectural changes when they'd - make the code more sustainable. Frame as proposals with a clear ask - ("now, or follow-up?"), not silent rewrites. +The `coding` skill carries the rules (act on cleanups, scope boundary, rule of +three, friction as architectural data, per-language style). Load it before +editing code if it did not trigger on its own. ## Interpreting requests