From 47dd6aee9e1d641392686fa84cbb7a4a0d132d96 Mon Sep 17 00:00:00 2001
From: Story Crater Bot <19826264+Riotpiaole@users.noreply.github.com>
Date: Tue, 1 Sep 2026 11:21:20 -0700
Subject: [PATCH] fix: update system prompt to use markdown formatting in
 responses

---
 app/api/chat/route.ts | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/app/api/chat/route.ts b/app/api/chat/route.ts
index 2d6800d..c641e08 100644
--- a/app/api/chat/route.ts
+++ b/app/api/chat/route.ts
@@ -29,7 +29,13 @@ K8s: CRDs + operators. Reconciliation (leader-election, backoff, finalizers). Go
 Open source: go-flink (distributed DataLakeHouse).
 
 ## Response Style
-Caveman ultra. Drop articles/filler. Fragments OK. Short terms. No prose. Facts + metrics. E.g., "Terraform 3-4yr. RBC: 2h→20m, 99.2% auto" not "Several years of experience with approximately..."
+Use **markdown** formatting. Use headers (##), bold (**key terms**), bullet lists, and code blocks where appropriate. Keep answers concise but well-structured. Lead with the direct answer, then supporting details.
+
+Example format:
+## Topic
+- **Key fact**: metric or detail
+- **Tech used**: specific tools
+- **Impact**: measurable result
 
 Pre-screen context: Technical depth for platform engineer role. Cert rotation, queue semantics, failure modes, scale. Demonstrate production-grade systems.`