You create a short learning element for a personal summary on the topic "{topic}".

KEYWORD FROM THE USER:
{hint}

CONTEXT (excerpts from the topic material):
{context}

Create EXACTLY ONE element for the keyword:
1. title — a concise title (max. 8 words, plain text, no Markdown/backticks)
2. description — what it is and what for: AT MOST 1–2 sentences
3. examples — EXACTLY ONE example: SHORT and SIMPLE, the minimal example in a topic-appropriate format (see EXAMPLE FORMAT), no real-world complexity.
4. hints — ALWAYS an empty list. The user adds hints later. (If ever required: TELEGRAPHIC style, max. 10 words.)

EXAMPLE FORMAT — align to the topic, not blanket to code:
- Code/tool topic (language, framework, CLI, configuration): a code block with language tag, a few lines, minimal example.
- Language topic (vocabulary, grammar, phrasing): 1–3 example sentences or a mini-dialogue, the foreign-language part in *italics*, German translation in parentheses where needed.
- Concept topic (psychology, communication, methods, theory): a mini-scenario in 2–4 sentences (situation → application → effect), a schema or a formula.
Mixed topics: per example, choose the format that shows the point most directly.
An example is always CONCRETE (real code, real sentences, a real situation) — never a description of what an example would show.
Each example names its variant: in code as a comment in the code syntax (e.g. `<!-- Einzelner Absatz -->`, `// Mit Default-Wert`), in prose as a leading **bold** label (e.g. **Höfliche Bitte:**).

The element is ATOMIC: understandable on its own, without the reader having read anything else. Resolve any terms used in a half-sentence.

Length: AS SHORT AS POSSIBLE, as long as needed — applies to description, examples and hints. Every word must earn its place: cut filler words, subclauses without informational value, and the self-evident. The length comes from the NUMBER of examples (variants), never from long texts.

Tone: clear German, direct, practical. Explain technical terms briefly on first use. No filler sentences, no introductory clichés.

Markdown in description and examples: normal paragraphs, `inline-code` for identifiers, **bold** sparingly for key points. No headings. Code examples ALWAYS as a code block with language tag (```sprache), never as inline code; prose examples (sentences, dialogues, scenarios) as plain text, NEVER forced into a code block. Identifiers, tags and commands (e.g. `<p>`, `git add`) in running text ALWAYS in backticks — never bare.

Write the element (title, description, examples) in GERMAN. Output ONLY valid JSON, no code fence, no other text:
{{"title": "...", "description": "...", "examples": ["```sprache\n...\n``` OR **Variante:** prose example"], "hints": []}}