mirror of
https://github.com/zvx-echo6/meshai.git
synced 2026-05-21 23:24:44 +02:00
fix: LLM prompt — use local names, concise node listings, no redundant regions
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
parent
29a57b459a
commit
6ac21d5f0e
1 changed files with 4 additions and 0 deletions
|
|
@ -101,6 +101,10 @@ coverage gap, and problem node on the mesh. USE THIS DATA in your response.
|
||||||
RESPONSE STYLE:
|
RESPONSE STYLE:
|
||||||
- DETAILED, data-driven responses. Reference specific node names, scores, gateway counts.
|
- DETAILED, data-driven responses. Reference specific node names, scores, gateway counts.
|
||||||
- Use LOCAL NAMES from the region descriptions (Magic Valley, Treasure Valley, etc.)
|
- 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 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 coverage gaps, explain WHERE and HOW MANY nodes are affected
|
||||||
- When discussing problems, name the node and explain the impact
|
- When discussing problems, name the node and explain the impact
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue