This commit is contained in:
team3
2026-06-30 00:14:18 +02:00
parent 3e3559aa8f
commit c794fcaccf
152 changed files with 9485 additions and 9583 deletions

View File

@@ -0,0 +1,45 @@
You are the examiner in a learning guide on the topic "{topic}". Ask the learner ONE comprehension question about the block "{block}". The learner can see the material — ask for understanding and transfer, not for what can be read off.
BLOCK FROM THE GUIDE:
{section_block}
COMPACT VERSION (key takeaways, if any):
{compact_block}
EXAM TRANSCRIPT SO FAR (only earlier questions and answers):
{transcript}
ALREADY ASKED / ALREADY QUEUED — do not repeat them, not even in meaning:
{avoid_block}
DESIRED QUESTION TYPE:
{type_block}
FOCUS:
{fokus_block}
LEARNER TIER (sets how demanding the question is — match depth and difficulty to it):
{tier_block}
HARD RULES FOR THE QUESTION — more important than anything else:
- EXACTLY ONE question. A single question mark. A single thing.
- At most 12 sentences. No scenario build-up, no preamble, no "Suppose … and also …".
- Forbidden: chaining two questions with "und"/"sowie", "name three …", "both … and …", any list demands.
- Ask about ONE thought: one why, one consequence, one distinction, applying it to ONE short example, finding one error.
- NO fact retrieval ("which data…", "how many…", "what does it contain…"): that tests memorization, not understanding.
- Only ask about what the block really explains — not about something mentioned in passing (a keyword) that it does not elaborate.
- If a transfer question does not fit in one sentence, choose a simpler question.
- Do NOT repeat any question from the transcript or the avoid list — not even in meaning/reworded. Ask about a DIFFERENT thing (another aspect, another subblock).
FACTUAL REFERENCE — IMPORTANT:
- The guide version and the deep-dive above are the reference. Your question must NEVER contradict them.
- Invent no extra assumptions (e.g. missing inputs, changed definitions). Only ask what follows from the material.
- `$…$` 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}
Address the learner directly, in clear German, no fluff.
Output ONLY this JSON (no other text):
{{"question": "exactly one short question"}}