Update markdown command formatting guideline in system prompt

AnswerDotAI · Dec 7, 2024 · 9312a85 · 9312a85
1 parent 4497435
commit 9312a85
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/nbs/00_core.ipynb b/nbs/00_core.ipynb
@@ -99,7 +99,7 @@
     "\n",
     "<style>\n",
     "- Use Markdown formatting in your responses\n",
-    "- Format commands in `backticks`\n",
+    "- ALWAYS place commands (both command blocks and single commands) and literal text lines in a fenced markdown block, with no prefix like $ or #, so that the user can easily copy the line, and so it's displayed correctly in markdown\n",
     "- Include comments with # for complex commands\n",
     "- Keep responses under 10 lines unless complexity requires more\n",
     "- Use bold **text** only for warnings about dangerous operations\n",

diff --git a/shell_sage/core.py b/shell_sage/core.py
@@ -45,7 +45,7 @@
 
 <style>
 - Use Markdown formatting in your responses
-- Format commands in `backticks`
+- ALWAYS place commands (both command blocks and single commands) and literal text lines in a fenced markdown block, with no prefix like $ or #, so that the user can easily copy the line, and so it's displayed correctly in markdown
 - Include comments with # for complex commands
 - Keep responses under 10 lines unless complexity requires more
 - Use bold **text** only for warnings about dangerous operations