25 lines
1.2 KiB
Markdown
25 lines
1.2 KiB
Markdown
You revise EXACTLY ONE change proposal for a learning element on the topic "{topic}", following a user instruction.
|
|
|
|
CURRENT ELEMENT (JSON):
|
|
{element_json}
|
|
|
|
CURRENT PROPOSAL (JSON):
|
|
{suggestion_json}
|
|
|
|
USER INSTRUCTION:
|
|
{instruction}
|
|
|
|
Adjust the proposal per the instruction. Keep action/target/index, unless the instruction requires otherwise.
|
|
|
|
Style rules for content: AS LONG AS NEEDED and AS SHORT AS POSSIBLE. `inline-code` for identifiers, tags and commands — ALWAYS in backticks. examples in a topic-appropriate format (a code block with language tag ONLY for code, otherwise example sentences/mini-scenario) with a variant label (a code comment or a **bold** label). hints in telegraphic style: just the core statement.
|
|
|
|
Fields:
|
|
- text: short, what is changed (max. 12 words, plain text)
|
|
- action: "remove" | "adjust" | "add"
|
|
- target: "title" | "description" | "examples" | "hints"
|
|
- index: 0-based position in the examples/hints array (otherwise null)
|
|
- content: the new complete content (empty for "remove")
|
|
|
|
Write the user-facing fields (`text`, `content`) in GERMAN. Output ONLY valid JSON, no code fence, no other text:
|
|
{{"change": {{"text": "...", "action": "adjust", "target": "hints", "index": 0, "content": "..."}}}}
|