From 4fbdc63ca364844c0166d3d4eabafb5cf8e7c2f3 Mon Sep 17 00:00:00 2001 From: Mario Zechner Date: Fri, 7 Aug 2026 22:55:48 +0200 Subject: [PATCH] docs: require clear concrete explanations --- AGENTS.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index fb6446da5..09eb963f0 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -6,6 +6,9 @@ - No emojis in commits, issues, PR comments, or code - No fluff or cheerful filler text (e.g., "Thanks @user" not "Thanks so much @user!") - Technical prose only, be direct +- Use concise, clear, simple language. Define unavoidable jargon before using it. +- Explain non-trivial designs and problems as: problem, concrete example or short trace, then solution. State why the solution is necessary and distinguish it from optional complexity. +- Prefer concrete behavior and small illustrations over abstract summaries, dense terminology, or unexplained lists of changes. - When the user asks a question, answer it first before making edits or running implementation commands. - When responding to user feedback or an analysis, explicitly say whether you agree or disagree before saying what you changed.