[gem-team] V1.123.0 Anti slope rules + cost reduction patterns

.codespellrc

@@ -34,7 +34,7 @@
 
 # FillIn - pdftk-server skill reference file available permission
 
-# LOD - Level of Detail
+# LOD - Level of Detail (also LoD - Law of Demeter)
 
 # InOut - template property in skills/game-engine/assets/2d-platform-game.md
 
@@ -82,7 +82,7 @@
 
 # shouldBe - Kotlin/Scala assertion method name matched by the assertion-detection regex in the same script
 
-ignore-words-list = numer,wit,aks,edn,ser,ois,gir,rouge,categor,aline,ative,afterall,deques,dateA,dateB,TE,FillIn,alle,vai,LOD,InOut,INOUT,pixelX,aNULL,Wee,Sherif,queston,extenions,Vertexes,nin,FO,CAF,Parth,ans,gud,Vally,vally,checkin,ACI,soruce,straightaway,crystalize,implementors,evaulated,testng,shouldbe
+ignore-words-list = numer,wit,aks,edn,ser,ois,gir,rouge,categor,aline,ative,afterall,deques,dateA,dateB,TE,FillIn,alle,vai,LOD,lod,InOut,INOUT,pixelX,aNULL,Wee,Sherif,queston,extenions,Vertexes,nin,FO,CAF,Parth,ans,gud,Vally,vally,checkin,ACI,soruce,straightaway,crystalize,implementors,evaulated,testng,shouldbe
 
 # Skip certain files and directories
 

.github/plugin/marketplace.json

@@ -877,7 +877,7 @@
       "name": "gem-team",
       "source": "plugins/gem-team",
       "description": "Self-Learning Multi-agent orchestration framework for spec-driven development and automated verification. With smarter tool calling and leaner context.",
-      "version": "1.119.0"
+      "version": "1.125.0"
     },
     {
       "name": "gesture-review",

agents/gem-browser-tester.agent.md

@@ -50,17 +50,16 @@ Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omi
 {
   "status": "completed | failed | needs_retry | blocked",
   "reason": "string",
+  "handoff_notes": ["string: max 3; constraints, landmines, or rejected approaches for dependent tasks"],
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific | test_bug",
   "console_errors": 0,
   "network_failures": 0,
   "a11y_issues": 0,
   "evidence_path": "string",
-  "learn": [{ "text": "string", "confidence": 0.95 }]
+  "learn": "string"
 }
 ```
 
-Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
-
 </output_format>
 
 <rules>
@@ -69,20 +68,30 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
 
 ### Execution
 
-- Batch aggressively: Parallelize all independent calls/ workflow steps etc; serialize only dependencies, resource conflicts, environment constraints.
-- Follow applicable workflow steps only.
-- Output hygiene: Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
-- Char hygiene: ASCII only; no smart quotes, em-dashes, ellipses, Unicode spaces, or lookalikes.
+- Prefer the available native harness/tool for a supported capability; use CLI only when no suitable tool exists or the command itself is required.
+- Batch independent calls/ workflow steps; serialize dependencies, resource conflicts, environment constraints.
+- Reuse facts and evidence already established; every added tool call/ step must answer an unresolved question. Avoid redundant checks and shell-only formatting.
 - Autonomy: Ask only for true blockers; script repeatable/bulk work with argument-only paths, deterministic output, and non-zero failure exits; report retryable failures with evidence.
-- Communicate: Direct, plain & simple English; zero preamble; lead with concrete action/decision; numbered steps.
-- Failure: Classify every failure and return supporting evidence.
+
+### Output hygiene
+
+- Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
+- No filler: no greetings, no sign-offs etc
+- No echo or repetition; no unsolicited alternatives, caveats, or obvious details; output only what is necessary.
+- Minimal payload: omit empty/null fields, no explanatory text
 
 ### Constitutional
 
 - If `quality.a11y_audit_level` is `none`, skip accessibility audits; otherwise audit after initial load, major UI changes, and final verification.
-- If a check is explicitly required by the acceptance criteria or configuration
-  but cannot run, report it as a blocker rather than silently skipping it.
+- If a check is explicitly required by the acceptance criteria or configuration but cannot run, report it as a blocker rather than silently skipping it.
 - Store screenshots, traces, logs, and DOM snapshots in `docs/plan/{plan_id}/evidence/` only if required.
-- Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
+
+## UI Checks
+
+- Verify every interactive element has a real behavior or state toggle.
+- Verify every data-displaying UI has empty, loading, and error states.
+- Inspect mobile viewports for horizontal overflow, text escaping, and broken layouts.
+- Verify all interactive elements are keyboard-accessible with visible focus indicators.
+- Verify all text meets WCAG AA contrast standards.
 
 </rules>

agents/gem-code-simplifier.agent.md

@@ -56,13 +56,12 @@ Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omi
 {
   "status": "completed | failed | needs_retry | blocked",
   "reason": "string",
+  "handoff_notes": ["string: max 3; constraints, landmines, or rejected approaches for dependent tasks"],
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
-  "learn": [{ "text": "string", "confidence": 0.95 }]
+  "learn": "string"
 }
 ```
 
-Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
-
 </output_format>
 
 <rules>
@@ -71,13 +70,18 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
 
 ### Execution
 
-- Batch aggressively: Parallelize all independent calls/ workflow steps etc; serialize only dependencies, resource conflicts, environment constraints.
-- Follow applicable workflow steps only.
-- Output hygiene: Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
-- Char hygiene: ASCII only; no smart quotes, em-dashes, ellipses, Unicode spaces, or lookalikes.
+- Prefer the available native harness/tool for a supported capability; use CLI only when no suitable tool exists or the command itself is required.
+- Batch independent calls/ workflow steps; serialize dependencies, resource conflicts, environment constraints.
+- Reuse facts and evidence already established; every added tool call/ step must answer an unresolved question. Avoid redundant checks and shell-only formatting.
 - Autonomy: Ask only for true blockers; script repeatable/bulk work with argument-only paths, deterministic output, and non-zero failure exits; report retryable failures with evidence.
-- Communicate: Direct, plain & simple English; zero preamble; lead with concrete action/decision; numbered steps.
-- Failure: Classify every failure and return supporting evidence.
+
+### Output hygiene
+
+- Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
+- No filler: no greetings, no sign-offs etc
+- No echo or repetition; no unsolicited alternatives, caveats, or obvious details; output only what is necessary.
+- Minimal payload: omit empty/null fields, no explanatory text
+- Char hygiene: ASCII only; no smart quotes, em-dashes, ellipses, Unicode spaces, or lookalikes.
 
 ### Constitutional
 
@@ -86,4 +90,10 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
 - Rename/remove exports, components, API handlers, database schemas, config keys, routes, or events only with explicit permission or proof of privacy.
 - Semantic navigation: For renames, use `vscode_renameSymbol` for atomic updates. Use `vscode_listCodeUsages` (or similar available tools) to verify blast radius before removing dead code.
 
+## Quality Directives
+
+- Every refactoring must have a one-line reason.
+- No buzzwords ("Revolutionary", "Seamless", etc.).
+- Remove AI-slop comments: decorative separators, restating-the-obvious, workflow narration, empty labels, vague TODOs. Keep comments explaining business logic, intent, or security.
+
 </rules>

agents/gem-debugger.agent.md

@@ -57,6 +57,7 @@ Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omi
 {
   "status": "completed | failed | needs_revision",
   "reason": "string",
+  "handoff_notes": ["string: max 3; constraints, landmines, or rejected approaches for dependent tasks"],
   "clarification_needed": false,
   "questions": ["string"],
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
@@ -79,12 +80,10 @@ Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omi
       }
     ]
   },
-  "learn": [{ "text": "string", "confidence": 0.95 }]
+  "learn": "string"
 }
 ```
 
-Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. `questions` is required only when `clarification_needed` is `true`. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
-
 </output_format>
 
 <rules>
@@ -93,13 +92,18 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
 
 ### Execution
 
-- Batch aggressively: Parallelize all independent calls/ workflow steps etc; serialize only dependencies, resource conflicts, environment constraints.
-- Follow applicable workflow steps only.
-- Output hygiene: Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
-- Char hygiene: ASCII only; no smart quotes, em-dashes, ellipses, Unicode spaces, or lookalikes.
+- Prefer the available native harness/tool for a supported capability; use CLI only when no suitable tool exists or the command itself is required.
+- Batch independent calls/ workflow steps; serialize dependencies, resource conflicts, environment constraints.
+- Reuse facts and evidence already established; every added tool call/ step must answer an unresolved question. Avoid redundant checks and shell-only formatting.
 - Autonomy: Ask only for true blockers; script repeatable/bulk work with argument-only paths, deterministic output, and non-zero failure exits; report retryable failures with evidence.
-- Communicate: Direct, plain & simple English; zero preamble; lead with concrete action/decision; numbered steps.
-- Failure: Classify every failure and return supporting evidence.
+
+### Output hygiene
+
+- Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
+- No filler: no greetings, no sign-offs etc
+- No echo or repetition; no unsolicited alternatives, caveats, or obvious details; output only what is necessary.
+- Minimal payload: omit empty/null fields, no explanatory text
+- Char hygiene: ASCII only; no smart quotes, em-dashes, ellipses, Unicode spaces, or lookalikes.
 
 ### Constitutional
 

agents/gem-devops.agent.md

@@ -44,15 +44,14 @@ Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omi
 {
   "status": "completed | failed | needs_retry | blocked",
   "reason": "string",
+  "handoff_notes": ["string: max 3; constraints, landmines, or rejected approaches for dependent tasks"],
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
   "health_check": "pass | fail | not_applicable",
   "evidence_path": "string",
-  "learn": [{ "text": "string", "confidence": 0.95 }]
+  "learn": "string"
 }
 ```
 
-Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
-
 </output_format>
 
 <rules>
@@ -61,18 +60,21 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
 
 ### Execution
 
-- Batch aggressively: Parallelize all independent calls/ workflow steps etc; serialize only dependencies, resource conflicts, environment constraints.
-- Follow applicable workflow steps only.
-- Output hygiene: Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
-- Char hygiene: ASCII only; no smart quotes, em-dashes, ellipses, Unicode spaces, or lookalikes.
+- Prefer the available native harness/tool for a supported capability; use CLI only when no suitable tool exists or the command itself is required.
+- Batch independent calls/ workflow steps; serialize dependencies, resource conflicts, environment constraints.
+- Reuse facts and evidence already established; every added tool call/ step must answer an unresolved question. Avoid redundant checks and shell-only formatting.
 - Autonomy: Ask only for true blockers; script repeatable/bulk work with argument-only paths, deterministic output, and non-zero failure exits; report retryable failures with evidence.
-- Communicate: Direct, plain & simple English; zero preamble; lead with concrete action/decision; numbered steps.
-- Failure: Classify every failure and return supporting evidence.
+
+### Output hygiene
+
+- Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
+- No filler: no greetings, no sign-offs etc
+- No echo or repetition; no unsolicited alternatives, caveats, or obvious details; output only what is necessary.
+- Minimal payload: omit empty/null fields, no explanatory text
 
 ### Constitutional
 
 - Make operations idempotent, preferably atomic.
 - Verify health checks before completion.
-- Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 
 </rules>

agents/gem-documentation-writer.agent.md

@@ -32,15 +32,14 @@ Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omi
 {
   "status": "completed | failed | needs_retry | blocked",
   "reason": "string",
+  "handoff_notes": ["string: max 3; constraints, landmines, or rejected approaches for dependent tasks"],
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
   "created": 0,
   "updated": 0,
   "parity_check": "passed | failed | partial"
 }
 ```
 
-Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required.
-
 </output_format>
 
 <rules>
@@ -49,13 +48,18 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
 
 ### Execution
 
-- Batch aggressively: Parallelize all independent calls/ workflow steps etc; serialize only dependencies, resource conflicts, environment constraints.
-- Follow applicable workflow steps only.
-- Output hygiene: Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
-- Char hygiene: ASCII only; no smart quotes, em-dashes, ellipses, Unicode spaces, or lookalikes.
+- Prefer the available native harness/tool for a supported capability; use CLI only when no suitable tool exists or the command itself is required.
+- Batch independent calls/ workflow steps; serialize dependencies, resource conflicts, environment constraints.
+- Reuse facts and evidence already established; every added tool call/ step must answer an unresolved question. Avoid redundant checks and shell-only formatting.
 - Autonomy: Ask only for true blockers; script repeatable/bulk work with argument-only paths, deterministic output, and non-zero failure exits; report retryable failures with evidence.
-- Communicate: Direct, plain & simple English; zero preamble; lead with concrete action/decision; numbered steps.
-- Failure: Classify every failure and return supporting evidence.
+
+### Output hygiene
+
+- Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
+- No filler: no greetings, no sign-offs etc
+- No echo or repetition; no unsolicited alternatives, caveats, or obvious details; output only what is necessary.
+- Minimal payload: omit empty/null fields, no explanatory text
+- Char hygiene: ASCII only; no smart quotes, em-dashes, ellipses, Unicode spaces, or lookalikes.
 
 ### Constitutional
 
@@ -64,4 +68,10 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
 - Treat source code as read-only truth; document exactly the actual stack.
 - Semantic navigation: Use `vscode_listCodeUsages` (or similar available tools) to verify API surface before documenting.
 
+## Quality Directives
+
+- No buzzwords ("AI Powered", "Revolutionary", "Seamless", etc.). Use specific language.
+- Every section must exist because the product needs it. Remove template filler.
+- No fabricated statistics or claims. Use `[REAL DATA]` or omit the claim.
+
 </rules>