Venice：Grok 4.6 四条提示技巧与模板

四条核心技巧

1. 角色 + 目标 + 完成定义：不要只说“帮我做一个 App”，要写清角色、一个具体目标，以及编号化的“Done means”。

2. 先锁定约束：提前说明技术栈、受众、语气、不能虚构的事实，以及需要先询问的范围扩展或破坏性操作。

3. 要求结构化输出：明确要表格、文件树、字段、补丁清单或步骤计划，避免得到一大段无法直接使用的散文。

4. 先设置 reasoning effort，再生成：简单改写使用 low/medium；复杂编码、多源研究使用 high/xhigh。后续每次只改变一个变量。

原文中的模板

多步骤研究简报（high）

You are a research analyst. Goal: produce a decision memo on [TOPIC] for [AUDIENCE]. Done means: (1) 5 key findings with sources labeled, (2) one recommendation, (3) three open risks. Constraints: do not invent statistics; flag missing data as questions. Return exactly those three sections — no intro essay.

代码库 / Agent 编码（high 或 xhigh）

You are a senior TypeScript engineer. Goal: propose a minimal fix for [BUG OR FEATURE] in this codebase description: [PASTE]. Done means: (1) root-cause hypothesis, (2) files to touch, (3) step plan under 8 steps. Constraints: no new dependencies unless essential; ask before expanding scope. After the plan, list two self-checks you would run before coding.

交互式产品第一版（medium 或 high）

You are a product engineer. Goal: turn this idea into a working first-version plan: [PRODUCT IDEA]. Done means: (1) user flows for the core loop, (2) screen list, (3) component map, (4) one sample UI copy block for the primary screen. Constraints: web app, mobile-first, no payments in v1. Prefer a substantial first structure over a thin outline. Stop after the four deliverables.

迭代规则

第一轮完成后，按“范围、约束、格式、推理档位”中的一个变量迭代；长任务追加“Verify assumptions, then continue. List what you tested.”，要求模型列出验证过的内容。