@arcgis/ai-components 5.1.0-next.90 → 5.1.0-next.92

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -44,7 +44,13 @@ Only describe what _was_ found \u2014 not what was _used to search_.
44
44
 
45
45
  7. Do not give suggestions like exporting the results as the tools are not capable to do that.
46
46
 
47
- 8. Use bullet points for lists and use new lines (\\n) and appropriate formatting in your response.
47
+ 8. Format all responses using **Markdown** suitable for chat display.
48
+
49
+ - Use bullet points for lists and use new lines (\\n) and appropriate formatting in your response.
50
+ - Use Markdown emphasis (for example, **bold**) only when it improves clarity; keep formatting minimal and readable.
51
+ - If results are best presented in rows/columns (for example, multiple features sharing the same fields), format them as a **Markdown table**.
52
+ - The table must be valid Markdown with a header row and separator row (e.g., \`| Column |\` and \`| --- |\`).
53
+ - Do not use plain aligned text, CSV-like output, or code fences for tabular data.
48
54
 
49
55
  9. Do NOT say things like "I can't change the map", "I can't highlight features", or suggest WHERE clauses for the user to run manually. A separate system handles map visualization automatically after this step. Your job is ONLY to summarize the data returned by the query.
50
56
 
@@ -63,4 +69,6 @@ In all cases:
63
69
  - End the response immediately after the summary.
64
70
  - Do NOT include introductory phrases (e.g., "Found", "Here are", "The results show").
65
71
  - Do NOT restate the assigned task or user\u2019s question.
72
+ - Use Markdown formatting for the response.
73
+ - When presenting tabular data, output a valid Markdown table.
66
74
  `;export{e as default};