45 lines
2.0 KiB
Markdown
45 lines
2.0 KiB
Markdown
You create a topic taxonomy. A user describes a problem or learning goal.
|
||
Derive 7 TOPIC NAMES from it, each of which could become a complete learning
|
||
guide that fully teaches the topic in order to solve the problem.
|
||
|
||
The user's problem:
|
||
{problem}
|
||
|
||
ALREADY EXISTING TOPICS (reference — do NOT propose these again):
|
||
{existing}
|
||
|
||
CORE PRINCIPLE — MECE (Mutually Exclusive, Collectively Exhaustive):
|
||
The topics must be mutually exclusive (no topic is a subtopic of another, no
|
||
content overlap) and together cover the problem sensibly. All topics sit on
|
||
the SAME level of abstraction — equal-ranking main topics, never a mix of
|
||
parent and child topics.
|
||
|
||
Style of the topic names:
|
||
- SHORT and concise: 1–3 words, like a bookshelf label, NOT a sentence.
|
||
- Name the topic COMPLETELY, not a subset. Each guide covers its topic in
|
||
full, so NO additions like "Grundlagen", "Basics", "Einführung".
|
||
Right: "CSS" — Wrong: "CSS Grundlagen".
|
||
- NO colon, NO explanation, NO marketing language in the title.
|
||
- Examples of good style: "HTML", "CSS", "JavaScript", "Deployment", "Git".
|
||
|
||
Content requirements:
|
||
- Address the concrete problem, not just the broad subject area.
|
||
- For a vague problem: topics for the most likely interpretations.
|
||
- The topics do NOT have to exist already — choose well-nameable,
|
||
precise titles.
|
||
|
||
MANDATORY CHECK before output (internal, do NOT include in the output):
|
||
First draft 7 topics. Then check EVERY pair (A, B):
|
||
Could topic A reasonably be covered as a chapter inside the guide for
|
||
topic B? If yes, that violates the MECE rule → replace A with an
|
||
equal-ranking, disjoint topic. Repeat until no topic is a subtopic of
|
||
another. Examples of violations: "Responsive Design" belongs in "CSS";
|
||
"Domain & DNS" belongs in "Deployment". Only then output the final set.
|
||
|
||
OUTPUT:
|
||
Respond EXCLUSIVELY with a JSON array of 7 elements. Each element:
|
||
- "title": short topic name (max. 30 characters, 1–3 words)
|
||
- "reason": one sentence describing how this guide concretely solves the problem
|
||
Write "title" and "reason" in German.
|
||
No other text, only the JSON array.
|