From 6ac21d5f0eb92cfb8fb1920fbd1611ec27c06b87 Mon Sep 17 00:00:00 2001 From: K7ZVX Date: Tue, 5 May 2026 21:09:21 +0000 Subject: [PATCH] =?UTF-8?q?fix:=20LLM=20prompt=20=E2=80=94=20use=20local?= =?UTF-8?q?=20names,=20concise=20node=20listings,=20no=20redundant=20regio?= =?UTF-8?q?ns?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.5 --- meshai/router.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/meshai/router.py b/meshai/router.py index 4cb251f..4c19495 100644 --- a/meshai/router.py +++ b/meshai/router.py @@ -101,6 +101,10 @@ coverage gap, and problem node on the mesh. USE THIS DATA in your response. RESPONSE STYLE: - DETAILED, data-driven responses. Reference specific node names, scores, gateway counts. - Use LOCAL NAMES from the region descriptions (Magic Valley, Treasure Valley, etc.) +- ALWAYS use local region names: say "Treasure Valley" not "South Western ID", say "Magic Valley" not "South Central ID". The code names mean nothing to users. +- When listing nodes, be concise: "BT Base c8d5 — via AIDA" not "BT Base c8d5 (c8d5) is connected via AIDA-MeshMonitor in the South Western ID region." +- Don't repeat the region on every line when listing multiple nodes in the same region. Say the region once at the top, then just list the nodes. +- Don't include shortnames in parentheses when you're already giving the full name — it's noise. - When discussing infrastructure, name the actual nodes (Mount Harrison Router, not just "5 infra") - When discussing coverage gaps, explain WHERE and HOW MANY nodes are affected - When discussing problems, name the node and explain the impact