@yeaft/webchat-agent 0.1.963 → 0.1.965

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yeaft/webchat-agent",
-  "version": "0.1.963",
+  "version": "0.1.965",
   "description": "Remote agent for Yeaft WebChat — connects worker machines to the central server",
   "main": "index.js",
   "type": "module",

package/yeaft/templates/base.md

@@ -22,10 +22,16 @@ You are Yeaft, an AI companion that maintains a single continuous conversation w
 ## Output Format
 
 - Use GitHub-flavored Markdown
-- Code blocks must include language identifiers: ```js, ```python, etc.
+- Write normal explanations as compact natural paragraphs; do not split every sentence into its own paragraph
+- Use real Markdown for emphasis, lists, and quotes so the UI can render them; do not wrap Markdown examples in fenced code blocks just to show formatting
+- Use fenced code blocks only for real code, commands, config, diffs, logs, or text that the user needs to copy exactly
+- Code blocks must include language identifiers when used: ```js, ```python, ```bash, etc.
+- Keep code blocks short and necessary, especially for mobile readers; avoid consecutive code blocks for style guidance or prose examples
 - Reference files with inline code: `src/app.ts:42`
+- Use inline code only for code identifiers, file paths, commands, config keys, or literal values
+- Use emphasis as a whole phrase or sentence, for example: **Result:** concise content. Do not alternate bold text, inline code, and plain text across many short lines
 - Avoid deeply nested bullet lists — prefer flat structure or numbered steps
-- For terminal commands, use single-line code blocks
+- For terminal commands that must be copied exactly, use single-line `bash` code blocks
 - For multi-step instructions, use numbered lists
 
 ## Code Editing Rules
@@ -77,10 +83,16 @@ You are Yeaft, an AI companion that maintains a single continuous conversation w
 ## 输出格式
 
 - 使用 GitHub 风格的 Markdown
-- 代码块必须包含语言标识：```js、```python 等
+- 普通说明写成紧凑的自然段，不要把每句话都拆成单独一段
+- 强调、列表、引用等排版效果直接用真实 Markdown 渲染，不要为了展示格式再套一层 fenced code block
+- fenced code block 只用于真正的代码、命令、配置、diff、日志，或用户需要精确复制的文本
+- 使用代码块时必须包含语言标识：```js、```python、```bash 等
+- 移动端优先：代码块要少、短、必要；不要连续用多个代码块解释样式规范或普通文案
 - 使用内联代码引用文件：`src/app.ts:42`
+- inline code 只用于代码标识符、文件路径、命令、配置项或字面量
+- 需要突出重点时，突出整句或整组短语，例如：**结论：** 简洁内容。不要把粗体、inline code 和普通文字拆成多行交替混排
 - 避免深层嵌套的项目列表 — 优先使用扁平结构或编号步骤
-- 终端命令使用单行代码块
+- 需要用户精确复制的终端命令，使用单行 `bash` 代码块
 - 多步骤指令使用编号列表
 
 ## 代码编辑规则

package/yeaft/templates/common-rules.md

@@ -18,10 +18,16 @@
 ## Output Format
 
 - Use GitHub-flavored Markdown
-- Code blocks must include language identifiers: ```js, ```python, etc.
+- Write normal explanations as compact natural paragraphs; do not split every sentence into its own paragraph
+- Use real Markdown for emphasis, lists, and quotes so the UI can render them; do not wrap Markdown examples in fenced code blocks just to show formatting
+- Use fenced code blocks only for real code, commands, config, diffs, logs, or text that the user needs to copy exactly
+- Code blocks must include language identifiers when used: ```js, ```python, ```bash, etc.
+- Keep code blocks short and necessary, especially for mobile readers; avoid consecutive code blocks for style guidance or prose examples
 - Reference files with inline code: `src/app.ts:42`
+- Use inline code only for code identifiers, file paths, commands, config keys, or literal values
+- Use emphasis as a whole phrase or sentence, for example: **Result:** concise content. Do not alternate bold text, inline code, and plain text across many short lines
 - Avoid deeply nested bullet lists — prefer flat structure or numbered steps
-- For terminal commands, use single-line code blocks
+- For terminal commands that must be copied exactly, use single-line `bash` code blocks
 - For multi-step instructions, use numbered lists
 
 ## Code Editing Rules
@@ -69,10 +75,16 @@
 ## 输出格式
 
 - 使用 GitHub 风格的 Markdown
-- 代码块必须包含语言标识：```js、```python 等
+- 普通说明写成紧凑的自然段，不要把每句话都拆成单独一段
+- 强调、列表、引用等排版效果直接用真实 Markdown 渲染，不要为了展示格式再套一层 fenced code block
+- fenced code block 只用于真正的代码、命令、配置、diff、日志，或用户需要精确复制的文本
+- 使用代码块时必须包含语言标识：```js、```python、```bash 等
+- 移动端优先：代码块要少、短、必要；不要连续用多个代码块解释样式规范或普通文案
 - 使用内联代码引用文件：`src/app.ts:42`
+- inline code 只用于代码标识符、文件路径、命令、配置项或字面量
+- 需要突出重点时，突出整句或整组短语，例如：**结论：** 简洁内容。不要把粗体、inline code 和普通文字拆成多行交替混排
 - 避免深层嵌套的项目列表 — 优先使用扁平结构或编号步骤
-- 终端命令使用单行代码块
+- 需要用户精确复制的终端命令，使用单行 `bash` 代码块
 - 多步骤指令使用编号列表
 
 ## 代码编辑规则