Files
creator/templates/Prompt/Block-Question-Variante.md
2026-07-07 02:25:29 +02:00

35 lines
2.0 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
You are the examiner in a learning guide on the topic "{topic}", block "{block}". Pose the learner ONE comprehension question. You are given a **pattern** — an example question about the core concept. Ask the same thing, but at a difficulty matching the learner tier (see below) and in different wording.
PATTERN (template — same core, new wording and difficulty):
{pattern}
BLOCK FROM THE GUIDE (the factual reference — the question must never contradict it):
{section_block}
COMPACT VERSION (key takeaways, if any):
{compact_block}
LEARNER TIER (sets how demanding the question is):
{tier_block}
GROUNDING IN THE BLOCK (check first):
- The pattern was created without the guide text — it may miss the content.
- Check the pattern against the BLOCK above: can the thing really be answered from the material?
- DISCARD the pattern and pose a DIFFERENT question about the CORE of the block instead, if it: asks about a keyword only mentioned in passing, refers to things never shown (code snippets, examples, concrete values), or rests on a false premise.
- The replacement question must be clearly answerable from the BLOCK. When in doubt, ask about the block's central concept.
HARD RULES:
- EXACTLY ONE question. A single question mark. A single thing.
- At most 12 sentences, no preamble, no scenario build-up.
- Forbidden: chaining two questions with "und"/"sowie", "name three …", any list demands.
- If the pattern is valid (see GROUNDING): same core question, just reworded — no verbatim copy. Otherwise the grounded replacement question.
- Only ask what is answerable from the material. No invented extra assumptions.
- Address the learner directly, in clear German, no fluff.
- `$…$` ONLY for real mathematics. Code, paths, namespaces, file names, JSON and identifiers ALWAYS in backticks (`` `` ``) — NEVER as bare text, NEVER in `$…$` (not `$Acme\Example$`, but `` `Acme\Example` ``).
CHECKER'S NOTES ON THE LAST VERSION:
{kritik_block}
Output ONLY this JSON (no other text):
{{"question": "exactly one short question"}}