Files
creator/templates/Prompt/Guide-Writer-Board.md
2026-07-06 20:57:41 +02:00

51 lines
3.6 KiB
Markdown

Write ONE section of a learning guide on the topic "{topic}" (format: {format_name}) — the block below, nothing else.
CHAPTER: {chapter}
BLOCK with its SUBBLOCKS and level labels (`[beginner]`/`[advanced]`/`[expert]`/`[peripheral]`):
{assignment}
LEARNING OBJECTIVES — after reading, a beginner must be able to do exactly this (a coverage gate checks the text against these objectives):
{ziele}
VERIFIED FACTS per subblock — binding basis. Quote cited facts (FACT[Source]) VERBATIM, invent nothing extra, do NOT re-research (a fact gate checks every claim against this list):
{facts}
{examples}
{gaps}
IMPORTANT — each subblock is delimited with a marker so the guide can later be shown in stages. The label comes EXACTLY from the assignment. Despite the marker, you write FLUENTLY and interwoven — the marker is an invisible interface, NOT a visible heading.
The content is INDEPENDENT of the level: every subblock is explained in a **beginner-friendly** way, no matter the label. The label only says WHEN in the learning path the point comes up (foundation → finesse) — NOT how complicated it is written.
The block gets TWO versions with the SAME subblocks (same titles, same order):
- **compact**: one mnemonic per subblock as a bullet (`- …`). For recall. Only name it, don't explain.
- **ausführlich** (detailed): the coherent beginner learning text.
HOW TO WRITE the detailed version — ONE coherent text for a junior who is learning the topic anew:
- Start with the anchor (framing): which problem / what for, tied to something familiar — BEFORE the first subblock marker. Mandatory.
- Resolve EVERY technical term at first mention in half a sentence. Use "Prerequisite" hints as anchors, "Hurdle" hints to clear misconceptions up front.
- Order of the subblocks as in the assignment: first `[beginner]`, then `[advanced]`, then `[expert]`, last `[peripheral]`.
- The NUMBER of subblocks is the depth signal: many subblocks → the block deserves length; few → keep it short. Never pad.
- LENGTH CAP for the detailed version: {budget} characters total — a HARD ceiling, not a target. Cover EVERY learning objective, but write DENSELY: fewer words, not more; prefer cutting a sentence to adding one. If you approach the cap, tighten — do not spill over. Overshooting gets rewritten.
- CONCISE: every sentence carries new information. No repetition, no filler, no preamble. When in doubt, leave it out.
- Show "how" procedures step by step. An example ONLY where it genuinely carries the understanding.
- If VERIFIED WORKED EXAMPLES are provided above, weave each into its subblock as instructed there; do NOT invent additional worked examples for subblocks that already have one.
SECTION SPECIFICATION:
{spec}
Write the entire guide content in GERMAN (the guide is for German-speaking learners), even though these instructions are in English.
Write ONLY the file {out_path} in EXACTLY this format — one kapitel marker, one section marker (title EXACTLY as in the assignment), a `compact` and an `ausführlich` block, each subblock with its `<!-- sub: LABEL | subblock title -->` marker (LABEL and title EXACTLY from the assignment, same order in both blocks):
<!-- kapitel: {chapter} -->
<!-- section: exact block title -->
<!-- compact -->
<!-- sub: beginner | exact subblock title -->
- mnemonic for this subblock (concise, no explanation)
<!-- ausführlich -->
Anchor: framing of the whole block — before the first subblock.
<!-- sub: beginner | exact subblock title -->
Beginner-friendly prose for this subblock.
No text outside the section, no document title, no table of contents.
{extra}