1. **Analyze User Input:**

• **Role:** World-Class Musicologist, Lead Music Educator, Master Arranger/Producer.
• **Task:** Write a comprehensive, deeply informative, engaging masterclass post about “Chord Quality Recognition: Major and Minor”.
• **Language:** STRICTLY German (de).
• **Branch/Category:** Ear Training Intensive.
• **Critical Directives:**
• NO generic/vague filler.
• SPECIFIC music theory details: exact intervals, semitone distances, harmonic/melodic techniques, voice leading, etc.
• PEDAGOGICAL STRUCTURE: 3 phases (Fundamentos, Desarrollo, Maestría).
• FORMATTING: GitHub-flavored Markdown, GitHub alerts (> [!NOTE], etc.), ASCII rhythm/chord grids, Practice Challenge, Key Terms Glossary.
• EMOJIS: Use naturally.
• COLORS: Highlight key musical terms using text or text.
• DEGREE COLOR SYSTEM: Use specific hex colors for scale degrees (I, II, III, IV, V, VI, VII). *Wait, the prompt says “For scale degrees, use these specific Hex colors: Degree I: #E53E3E, Degree II: #38A169…” but the syntax text is also specified. I’ll stick to the text syntax for general terms, and apply the hex colors to scale degrees if mentioned, or just follow the exact syntax requested. The prompt says “Highlight key musical terms using text or text.” I’ll use that. For degrees, I’ll use the hex colors as specified, maybe in markdown link format or just inline style if needed, but I’ll stick to the requested syntax. Actually, the prompt says “Use these specific Hex colors: Degree I: #E53E3E…”. I’ll format degrees like I or just use the hex directly if the platform supports it, but I’ll follow the exact syntax text to be safe, or just use standard markdown with the hex. I’ll stick to text for general terms and apply the hex to degrees as requested: I.
• DIDACTIC TOOLS: Markdown Tables and Lists.
• STRICTLY FORBIDDEN: YAML, JSON, structured data blocks. Pure Markdown.
• Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary. (Wait, the prompt says “Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary.” BUT also says “PEDAGOGICAL STRUCTURE (Divide into 3 distinct learning phases): Phase 1: Fundamentos, Phase 2: Desarrollo, Phase 3: Maestría”. I need to reconcile this. I’ll use the requested structure but integrate the 3 phases within it, or adapt the headings to match the pedagogical structure while keeping the overall flow. I’ll follow the explicit structure: # Titel, ## Einführung, ## Hauptkonzept (divided into the 3 phases), ## Beispiele, ## Praktische Zusammenfassung. Actually, I’ll make the phases the core of the Main Concept section.)
• ADDITIONAL INSTRUCTIONS: This part is confusing. It says “The post.content field contains HTML… Translate ONLY the visible text content to de while preserving the exact HTML structure… CRITICAL: Preserve all placeholder markers like __MUSICXML_BLOCK_0__… STRICTLY FORBIDDEN: Do NOT generate or mention ‘MusicXML’… Return the translated HTML content with the title translated.”
• WAIT. This is a major contradiction. The prompt starts with “Your task is to create clear, focused, educational content in Markdown format.” and gives detailed Markdown formatting rules. Then at the end, it says “The post.content field contains HTML with music theory content. Translate ONLY the visible text content to de while preserving the exact HTML structure… Return the translated HTML content with the title translated.”
• This looks like a prompt injection or a copy-paste error from another task. The user provided an “ORIGINAL DRAFT/TOPIC TO ENRICH & TRANSFORM:” in Markdown, not HTML. The additional instructions talk about HTML translation, which doesn’t match the provided draft. I should prioritize the main instructions (Markdown, German, 3 phases, formatting rules) and ignore the contradictory HTML translation instruction, as it’s likely a template artifact. I will produce the output in pure Markdown as requested in the main body, in German, following all the specific formatting and pedagogical rules. I will explicitly follow the Markdown structure and ignore the HTML translation directive since there’s no HTML in the draft.

2. **Deconstruct Requirements & Plan Content (in German):**

• **Language:** German.
• **Topic:** Erkennung von Akkordqualitäten: Dur und Moll (Chord Quality Recognition: Major and Minor).
• **Category:** Ear Training Intensive.
• **Structure:**
• # Titel
• ## Einführung
• ## Hauptkonzept (with Phases 1, 2, 3)
• ## Beispiele
• ## Praktische Zusammenfassung
• **Formatting:** GitHub alerts, emojis, color syntax text, degree hex colors, tables, lists, ASCII grids, practice challenge, glossary.
• **Content Depth:** Specific intervals, semitone distances, voice leading, harmonic context, practical ear training techniques, exact chord voicings, rhythmic/harmonic integration.
• **Phases:**
• Phase 1: Fundamentos (The Seed) — Core pattern & foundational harmony.
• Phase 2: Desarrollo (The Growth) — Voicings, piano/guitar patterns, arrangement.
• Phase 3: Maestría (The Flower) — Advanced reharmonization, pro tricks, improvisation nuances.
• **Color System:** I’ll use Dur, Moll, Terz, etc. For degrees: I, III, V.
• **Tables/Lists:** Semitone distances, chord structures, practice routines.
• **ASCII:** Chord diagrams or interval grids.
• **Glossary:** Key terms in German.
• **Language:** Strictly German.
  Let’s draft step-by-step in German.
  **Title:** # 🎵 Erkennung von Akkordqualitäten: Dur und Moll
  **Introduction:** Brief, focused on ear training. Introduce the core concept: distinguishing major/minor by the third. Use color syntax. Mention it’s the foundation for all harmonic listening.
  **Main Concept:** Divide into the 3 phases.
• *Phase 1: Fundamentos (Der Samen)*: Focus on interval structure, semitone distances, the critical third. Table of intervals. ASCII grid for piano keyboard showing semitones.
• *Phase 2: Desarrollo (Das Wachstum)*: Voicings, voice leading, rhythmic context, how to practice actively. Piano/guitar patterns. Table of voicings.
• *Phase 3: Maestría (Die Blüte)*: Modal interchange, extended chords (maj7, min7), harmonic context, pro ear training tricks, singing inner voices.
  **Examples:** Concrete progressions, how they sound, how to train.
  **Practical Summary:** Practice challenge, checklist, glossary.
  **Formatting Checks:** GitHub alerts, emojis, color syntax, degree hex colors, tables, lists, ASCII, pure Markdown.
  Let’s write it out carefully in German, ensuring all constraints are met.
  *Self-Correction/Refinement during planning:*
• The prompt says: “Highlight key musical terms using text or text.” I’ll use this exact syntax.
• “For scale degrees, use these specific Hex colors: Degree I: #E53E3E, Degree II: #38A169, Degree III: #ECC94B, Degree IV: #06B6D4, Degree V: #ED8936, Degree VI: #3182CE, Degree VII: #9333EA.” I’ll format them as I, etc.
• Structure must be exactly: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary. I will embed the 3 phases inside ## Main Concept.
• I need to include GitHub alerts: > [!NOTE], > [!TIP], > [!IMPORTANT].
• ASCII rhythm/chord grids: I’ll create a simple piano key grid for intervals and a chord voicing grid.
• Practice Challenge / Reto Práctico section.
• Key Terms Glossary at the end.
• Language: German.
• No HTML translation stuff (ignoring the contradictory instruction as it’s clearly a template mismatch).
• I will strictly follow the Markdown structure and formatting rules.
  Draft Generation (Mental Translation & Structuring):
  # 🎹 Erkennung von Akkordqualitäten: Dur und Moll
## Einführung
  …focus on ear training, the third, semitones, color syntax…
  ## Hauptkonzept
### Phase 1: Fundamentos (Der Samen) 🌱
  …interval structure, table, ASCII grid, color syntax…
  ### Phase 2: Desarrollo (Das Wachstum) 🌿
  …voicings, voice leading, piano/guitar patterns, table…
  ### Phase 3: Maestría (Die Blüte) 🌸
  …extended chords, modal interchange, pro tricks, harmonic context…
  ## Beispiele
  …concrete progressions, ear training context…
  ## Praktische Zusammenfassung
  …Practice Challenge, Glossary…
  Check constraints: Emojis? Yes. Colors? Yes. Degree hex? Yes. Tables/Lists? Yes. GitHub alerts? Yes. ASCII? Yes. Structure? Yes. Language? German. No YAML/JSON? Yes. Pure Markdown? Yes.
  Let’s write it out carefully. I’ll pay close attention to the exact syntax for colors and degrees. I’ll use Terz or similar. The prompt says text or text. I’ll stick to blue/red for key terms, and hex for degrees.
  I’ll make sure the musical theory is precise: 0-4-7 for major, 0-3-7 for minor. Semitone distances. Voice leading: common tone (root & fifth), moving third. Harmonic context: I, IV, V in major vs i, iv, v in minor. Extended chords: Imaj7 vs im7. Modal interchange: borrowing from parallel minor/major.
  I’ll incorporate all pedagogical phases under Main Concept.
  I’ll add GitHub alerts strategically.
  I’ll create ASCII grids for piano intervals and chord shapes.
  I’ll write everything in German.
  Proceed.
  Structure check:
  

  Titel

Einführung

Hauptkonzept

Phase 1…

Phase 2…

Phase 3…

Beispiele

Praktische Zusammenfassung

Reto Práctico / Practice Challenge

Glossar

All constraints met. Generating.
Self-Correction/Note during thought: The prompt says “Highlight key musical terms using text or text.” I will use this exact Markdown-like syntax. For degrees, I’ll use I etc. as requested. I’ll ensure the tone is expert, pedagogical, and focused on ear training. I’ll avoid fluff. I’ll strictly follow the structure. I’ll translate the original draft’s concepts but expand them significantly with the required depth. All good.
Output matches the response.
Generating.
[Output Generation] -> *Proceeds*
*(Self-Correction/Verification during drafting)*:
- Check color syntax: text is not standard Markdown, but the prompt explicitly requests it. I will use it exactly as written.
- Check degree colors: I etc.
- Check structure: Exactly as requested.
- Check language: Strictly German.
- Check forbidden items: No YAML, JSON, HTML, MusicXML mentions outside placeholders (but I won’t use placeholders since the draft didn’t have them, and the prompt says preserve if present. I’ll just ignore the HTML instruction as it’s contradictory to the main task).
- I’ll make sure the content is highly technical and focused on ear training.
- I’ll add the ASCII grids and tables.
- I’ll include the GitHub alerts.
- All set.🎵
Output generation.
*[Done.]*

Einführung

Die Fähigkeit, Akkordqualitäten im Gehör zu unterscheiden, ist das Fundament jeder harmonischen Wahrnehmung. Sobald Intervalle sicher identifiziert werden können, rücken Dreiklänge in den Fokus. Der entscheidende Unterschied zwischen Dur und Moll liegt nicht im Stammton oder der Quinte, sondern ausschließlich in der Terz. Dieser einzelne Halbtonschritt verändert die gesamte emotionale und funktionale Ausstrahlung eines Akkords. In dieser Masterclass trainieren wir Ihr Ohr systematisch, um diese Farbeinstellung sofort und ohne Instrument zu erkennen.

[!IMPORTANT]
Konzentrieren Sie sich beim ersten Hören ausschließlich auf die Terz. Sie ist der harmonische „Schlüssel“, der die Qualität definiert. Stammton und Quinte bleiben bei Dur und Moll identisch.

Hauptkonzept

Phase 1: Fundamentos (Der Samen) 🌱

Die grundlegende Struktur beider Akkordqualitäten basiert auf exakten Halbtonschritten (ST) vom Grundton aus. Das Ohr muss diese Distanzen internalisieren, bevor es sie im Kontext erkennen kann.

**Piano-Intervall-Grid (ASCII):**

C (Stammton) ──● C
│ 1 ST
│ 2 ST
│ 3 ST → m3 (Moll-Terz)
│ 4 ST → M3 (Dur-Terz) ← KRISENGRENZE
│ 5 ST
│ 6 ST
│ 7 ST → P5 (Reine Quinte)
└──● G

[!NOTE]
Der Unterschied von genau **einem Halbton** zwischen m3 und M3 ist der einzige strukturelle Unterschied. Trainieren Sie, diesen Halbtonschritt als „Farbwechsel“ zu hören, nicht als neue Note.

Phase 2: Desarrollo (Das Wachstum) 🌿

Im praktischen Spiel manifestiert sich die Qualität durch spezifische Stimmführungen und Voicings. Das Ohr lernt am schnellsten, wenn es die terzdefinierte Note in verschiedenen Oktaven und Instrumentenregistern verortet.
**Voicing-Vergleich (Close Position, Klavier/Gitarre):**

Dur-Dreiklang (C-E-G): Moll-Dreiklang (C-E♭-G):
┌────┬────┬────┐ ┌────┬────┬────┐
│ G │ E │ C │ │ G │ E♭ │ C │
└────┴────┴────┘ └────┴────┴────┘
5 3 1 5 3 1

**Praktische Anwendungstechniken:**
1. **Common-Tone-Voice-Leading:** Bei der Umwandlung von Dur zu Moll (und umgekehrt) bleiben Stammton I und Quinte V stehen. Nur die Terz bewegt sich um einen Halbton. Hören Sie diese minimale Bewegung isoliert.
2. **Rhythmisches Verankern:** Spielen Sie die Akkorde im 4/4-Takt mit einem klaren Accent auf Schlag 1. Die emotionale Wirkung verstärkt sich, wenn die Terz rhythmisch betont oder leicht anticipiert wird.
3. **Instrumentale Kolorierung:** Am Piano klingt der Dur-Dreiklang in der Grundstellung breiter und offener. Am E-Gitarre (Standardstimmung) erzeugt die gleiche Noteabfolge im 5. Bund (A-Dur) einen klanglich „vorwärtsdrängenden“ Charakter, während A-Moll im 5. Bund (Finger 5-7-7) eine gedämpftere, innere Spannung zeigt.

[!TIP]
Singen Sie die [Terz](color:red