Files
creator/templates/Prompt/Relevance-Research.md
2026-07-04 02:32:31 +02:00

2.3 KiB

Rate each subblock of the topic "{topic}" by relevance: relevant or peripheral. The relevance controls whether a point goes into the focused guides or only into the complete guide.

SUBBLOCKS (in brackets the parent block of the number; many state their core points with "Kern:"): {subblocks}

Use the core points for a well-grounded rating — judge on the content, not just the title.

Relevance:

  • relevant: core/standard knowledge that CARRIES the topic — central concepts, definitions, properties, common practice. For practical topics: what you need in actual use. For theoretical topics: central theorems/properties, EVEN without practical use. What you genuinely should know.
  • peripheral: a side note, special/niche case, "nice to know", deprecated/exotic — PLUS purely historical details (who/when), concrete numeric examples of a general principle, mere cross-references. NOT peripheral: a central theorem or a fundamental property just because it seems "theoretical". Belongs only in a complete guide.

Rules:

  • These subblocks all already belong to the topic — the question is not whether but how central. Judge core vs. peripheral within its own block, one at a time.
  • The basic syntax / core rule of a block — what the block TITLE promises — is NEVER peripheral. A block "Headings" without its heading syntax marked relevant is broken. Check this per block before anything else.
  • When the BLOCK itself is a fringe/extension feature (non-standard, niche, an add-on rather than core of the topic), only its basic syntax and purpose are relevant — its detail rules and special cases are peripheral. A fringe feature must not be decomposed deeper than the core topics (measured: a non-standard block carried 22 "relevant" detail rules while core blocks had 6).
  • peripheral is a genuine category for clear cases: nice-to-know, special/niche cases, detail/numeric examples, historical notes, cross-references, style tips.
  • peripheral items are CUT from the focused guides — a wrong peripheral loses content, a wrong relevant only adds a paragraph. When in doubt → relevant.
  • Only judge — invent nothing, change no subblocks.

Reply with ONLY the JSON — no other text, no code fences.

Format (exactly one value for EACH number; no other text): {{"relevance": {{"1": "relevant", "2": "peripheral", "3": "relevant"}}}} {extra}