ed/manual_slop
Private
Public Access
0
0
Fork 0
Code Activity

docs(agents): tier4 prompt — read bans in §17 before diagnosing errors

Browse Source
This commit is contained in:
Edward R. Gonzalez
2026-06-25 21:25:30 -04:00
parent 01bfb92814
commit 1427ac92cf
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.opencode/agents/tier4-qa.md
+2
View File
@@ -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: