JEV GUIDE

Jev 提示词怎么写？Choice、Score、Noul 示例

Jev 提示词的起点是定义判断条件。先明确程序需要什么值，再写题目和候选项。本文的编辑建议与合成示例没有经过真实模型复测。

Jev Gallery · 内容核对 2026-09-19

把含糊目标改成可检查的问题

“判断这个反馈好不好”很难验证。可以拆成“是否描述故障”“属于哪类功能”“复现信息完整到哪一级”。让每个问题只承担一项责任。

官方文档指出，问题 ID 不会传给模型。因此，即使把键命名为 has_steps，也必须在 instructions 中说明判断对象和复现步骤的定义。

依据: TypeSafe · Questions ↗

题型跟着答案走

要把反馈放入一个队列，用 Choice；要按明确定义的完整度分级，用 Score；只检查是否满足一个条件，用 Noul。

下面是题目片段，需要与 state 和 model 组合成完整请求。候选项保留 other，让不适合现有类别的输入有出口。

JSON

{
  "route": {
    "type": "choice",
    "instructions": "Which queue best matches the main request in `report`?",
    "criteria": {
      "bug": "A feature behaves differently from an explicitly described expectation.",
      "idea": "A request to add or change functionality without a described failure.",
      "other": "Unclear, unrelated, or insufficient information."
    }
  },
  "detail": {
    "type": "score",
    "instructions": "How much reproduction information is explicitly present in `report`?",
    "criteria": [
      "No specific action or outcome.",
      "An action and unexpected outcome are described.",
      "Actions, expected outcome, and environment are described."
    ]
  },
  "has_environment": {
    "type": "noul",
    "instructions": "Does `report` explicitly name a browser, operating system, or application version?"
  }
}

依据: TypeSafe · Questions ↗