From 1427ac92cf519abd7d45c33e5f2f5917e9493629 Mon Sep 17 00:00:00 2001 From: Ed_ Date: Thu, 25 Jun 2026 21:25:30 -0400 Subject: [PATCH] =?UTF-8?q?docs(agents):=20tier4=20prompt=20=E2=80=94=20re?= =?UTF-8?q?ad=20bans=20in=20=C2=A717=20before=20diagnosing=20errors?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .opencode/agents/tier4-qa.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.opencode/agents/tier4-qa.md b/.opencode/agents/tier4-qa.md index cacc38eb..c391aeb2 100644 --- a/.opencode/agents/tier4-qa.md +++ b/.opencode/agents/tier4-qa.md @@ -24,6 +24,8 @@ ONLY output the requested analysis. No pleasantries. You operate statelessly. Each analysis starts fresh. Do not assume knowledge from previous analyses or sessions. +**However (added 2026-06-27):** the canonical conventions are in the docs. Read `conductor/code_styleguides/data_oriented_design.md` §8.5 and `python.md` §17 BEFORE diagnosing. Many Tier 2 errors stem from LLM default patterns (`dict[str, Any]`, `Optional[T]`, `hasattr()` dispatch, local imports). Knowing the bans helps you identify whether the bug is a pattern violation vs a logic error. + ## Architecture Reference When analyzing errors, trace data flow through thread domains documented in: