update

templates/Prompt/Blocks-Dependency.md

@@ -0,0 +1,17 @@
+A small block for the topic "{topic}" may be a sub-topic of a bigger block. Pick the ONE block it belongs under — or 0 if it stands on its own after all.
+
+SMALL BLOCK:
+{small}
+
+CANDIDATE PARENT BLOCKS:
+{parents}
+
+Rules:
+- Pick the number of the block the small block is a detail/sub-step/property of.
+- 0 = it is NOT a sub-topic of any of them (it is actually standalone).
+- Only pick a parent if the small block clearly belongs INSIDE it.
+
+Write ONLY the JSON file to: {out_path}
+
+Format (the chosen parent number, or 0):
+{{"parent": 0}}

templates/Prompt/Blocks-Filter-Check.md

@@ -0,0 +1,23 @@
+You are filtering the block inventory of a learning guide for the topic "{topic}". Judge the ONE block below.
+
+BLOCK:
+{title} — {content}
+
+## Question
+Is this a **valid, self-contained learning block** that genuinely belongs to "{topic}"?
+
+- **keep = true** → a real, teachable concept of this topic: a method, definition, syntax element, problem, rule, or feature. The default.
+- **keep = false** → drop it, ONLY if it clearly is one of:
+  - **Off-topic**: not actually about "{topic}" (a stray crawl artifact, a different subject).
+  - **Noise / meta**: navigation, "Table of Contents", "Dos and Don'ts", a tool/website name, a page section — not a concept you would learn.
+  - **Empty / degenerate**: title says nothing teachable, or the content is a non-statement.
+
+## Rules
+- When in doubt → **keep** (true). Only drop a CLEAR off-topic / noise / empty case.
+- Judge by the CONTENT (after the "—"), not only the title.
+- Do NOT drop something just because it is narrow or overlaps another block — that is handled elsewhere. Drop only off-topic / noise / empty.
+
+Write ONLY the JSON file to: {out_path}
+
+Format:
+{{"keep": true}}

templates/Prompt/Blocks-Naming-Check.md

@@ -0,0 +1,15 @@
+The numbered entries below all describe the SAME block for the topic "{topic}". Entry number {current} was chosen as the canonical title. Check whether that is the best choice — if another entry is a clearly better canonical name, pick it instead.
+
+MEMBERS:
+{members}
+
+Rules:
+- Pick an EXISTING entry number — do NOT invent a title.
+- Best = most concrete, precise, self-explanatory, established term for the shared concept.
+- If the current choice ({current}) is already the best, return it unchanged.
+- When in doubt, keep the current choice.
+
+Write ONLY the JSON file to: {out_path}
+
+Format (the best member number, nothing else):
+{{"best": {current}}}

templates/Prompt/Blocks-Naming.md

@@ -0,0 +1,15 @@
+The numbered entries below all describe the SAME block (concept) for the topic "{topic}", just worded differently. Pick the ONE entry whose title is the best canonical name for this block.
+
+MEMBERS:
+{members}
+
+Rules:
+- Pick an EXISTING entry — do NOT invent a new title or umbrella term.
+- Prefer the most CONCRETE, precise, self-explanatory title for the shared concept.
+- Prefer the established/standard term (correct spelling, full form over cryptic abbreviation) — but stay concrete, never over-general.
+- Avoid reference/placeholder titles ("Satz 7.18", "Punkt 3", "(**)") if a meaningful one exists.
+
+Write ONLY the JSON file to: {out_path}
+
+Format (the chosen member number, nothing else):
+{{"best": 1}}

templates/Prompt/Blocks-Research.md

@@ -17,7 +17,8 @@ Rules:
 - Write title and description in GERMAN (technical terms/code identifiers stay original).
 - Description at most ~12 words.
 
-Write ONLY the Markdown file to: {blocks_path}
+Write the Markdown file to: {blocks_path}
+**Stream INCREMENTALLY — your output is read LIVE while you work.** The MOMENT you find a block: (1) print its line in your reply, AND (2) re-write the file with all blocks so far. One line per block, immediately, do NOT wait until the end. Cards appear as soon as a line lands.
 
 Format: EXACTLY one line per block: `N. Title — Kurzbeschreibung — Source`
 The source (3rd segment) MUST be the exact file name or URL of the crawl page the block comes from — it drives the coverage check.

templates/Prompt/Blocks-Small.md

@@ -0,0 +1,15 @@
+Below are block candidates for the topic "{topic}". For EACH, decide whether it is a STANDALONE learning block or a SMALL fragment.
+
+BLOCKS:
+{blocks}
+
+Rules:
+- small = true → a property, detail, sub-step or notation that only makes sense inside another block
+  (e.g. "install() method" belongs to "Plugin lifecycle"; "Knapsack ∈ NP" belongs to "Knapsack").
+- small = false → a self-contained learning unit (its own problem/method/concept).
+- When in doubt → false (keep as a main block).
+
+Write ONLY the JSON file to: {out_path}
+
+Format (each block number → true/false):
+{{"small": {{"1": true, "2": false}}}}