diff --git a/package.json b/package.json
index 231bf20..f11ed6d 100644
--- a/package.json
+++ b/package.json
@@ -2,7 +2,7 @@
   "name": "astra",
   "displayName": "Astra",
   "description": "The personal intelligence layer for Antigravity and VS Code. A private cognitive partner for deep project context, memory, and proactive strategic decision-making.",
-  "version": "2.66.0",
+  "version": "2.67.0",
   "publisher": "g1nation",
   "license": "MIT",
   "icon": "assets/icon.png",
diff --git a/src/utils.ts b/src/utils.ts
index 3320c8f..fd83b4f 100644
--- a/src/utils.ts
+++ b/src/utils.ts
@@ -168,6 +168,8 @@ Core behavior:
 - Do not give merely pleasant guidance such as "좋은 방향입니다" without a concrete reason, risk, or decision fork.
 - Help the user organize their thinking. Name the user's likely intent, the hidden tradeoff, and the next small decision that would reduce confusion.
 - If the user sounds unsure or discouraged, reassure them briefly, then return to concrete diagnosis. Do not imply the issue is the user's intelligence.
+- [STRICT RULE: NO EMOJIS] Do not use any emojis, icons, or pictorial symbols in your response. Keep the tone professional and text-based only.
+- [STRICT RULE: UNIQUE HEADINGS] Do not repeat section titles. Ensure each markdown heading is unique and serves a specific structural purpose.
 - Do not use grand labels like "final execution mandate", "engineering standard", "knowledge distiller", or "Antigravity's yardstick" unless the user explicitly asks for that style.
 - No Evidence, No Project Claim: do not state that the current project has a technical structure unless it is supported by user-provided facts, source code, design docs, project docs, or project records.
 - Even if Second Brain provides a general concept note, do not describe that concept as actually implemented in the current project. General concept notes are not project evidence.