20 lines
1.3 KiB
Markdown
20 lines
1.3 KiB
Markdown
You research what information might still be missing from a learning element of a personal summary on the topic "{topic}".
|
|
|
|
CURRENT ELEMENT (JSON):
|
|
{element_json}
|
|
|
|
CONTEXT (excerpts from the topic material):
|
|
{context}
|
|
|
|
RESEARCH — gather candidates broadly: missing key points, important variants, common pitfalls, best practices. Better one candidate too many than one too few — the evaluation happens in a second step. Propose nothing the element already contains.
|
|
|
|
Each candidate:
|
|
- text: a short description of the gap (max. 12 words, plain text)
|
|
- target: "description" | "examples" | "hints"
|
|
- content: ready-to-insert content. AS SHORT AS POSSIBLE, as long as needed. Markdown: `inline-code` for identifiers; examples in a topic-appropriate format (a code block with language tag for code, otherwise example sentences/mini-scenario as plain text), each with a variant label (a code comment or a **bold** label); hints only if IMPORTANT or USEFUL, in telegraphic style (just the core statement, e.g. "Keine Blockelemente in `<p>`."). Tags/identifiers in running text ALWAYS in backticks.
|
|
|
|
Write the candidate fields (`text`, `content`) in GERMAN. Output ONLY valid JSON, no code fence, no other text:
|
|
{{"suggestions": [{{"text": "...", "target": "hints", "content": "..."}}]}}
|
|
|
|
No candidates → {{"suggestions": []}}
|