1. **Analyze User Input:**

• **Role:** World-Class Musicologist, Lead Music Educator, Master Arranger/Producer.
• **Task:** Write a comprehensive, deeply informative, and engaging masterclass post about a musical topic/style.
• **Language:** STRICTLY German (de).
• **Branch/Category:** Piano Fundamentals.
• **Critical Directives:**
• NO generic/vague filler.
• PROVIDE SPECIFIC, CONCRETE MUSIC THEORY DETAILS: exact chord progressions, rhythmic breakdown, harmonic/melodic techniques, historical context, key artists, landmark recordings.
• PEDAGOGICAL STRUCTURE: 3 phases (Fundamentos, Desarrollo, Maestría).
• FORMATTING: GitHub-flavored Markdown, alerts (> [!NOTE], etc.), ASCII rhythm grids/chord boxes, Practice Challenge section, Key Terms Glossary.
• **Original Draft/Topic:** Seventh Chords and Inversions (provided in English).
• **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…”. But the prompt also says “Write the complete, expert-level masterclass post in Markdown format”. The additional instructions seem to be a copy-paste from a different task (HTML translation). I need to reconcile this. The main prompt says “create clear, focused, educational content in Markdown format” and gives a specific structure. The additional instructions contradict the markdown requirement by asking to preserve HTML. I will prioritize the main prompt’s explicit instructions (Markdown, specific structure, German language, specific formatting like alerts, ASCII grids, 3 phases, glossary) and ignore the HTML translation constraint as it’s likely a template error. I will strictly follow the Markdown structure and content requirements. I will make sure the output is pure Markdown in German.
  Let’s re-read carefully: “You are a World-Class Musicologist… Your objective is to write a comprehensive, deeply informative, and engaging masterclass post about the musical topic/style.” Then it gives the original draft. The additional instructions at the end seem to be a strict template override, but it explicitly says “Translate ONLY the visible text content to de while preserving the exact HTML structure…”. This is a direct contradiction to “write the complete, expert-level masterclass post in Markdown format”. I will assume the Markdown requirement and the detailed pedagogical structure override the HTML translation note, as the HTML note is likely a leftover from another prompt. I will produce a pure Markdown response in German, following all the pedagogical and formatting directives.
  Key elements to include:
• Language: German
• Topic: Seventh Chords and Inversions (Siebter-Akkorde und Umkehrungen)
• Structure: # Title, ## Introduction, ## Phase 1: Fundamentos, ## Phase 2: Desarrollo, ## Phase 3: Maestría, ## Practice Challenge, ## Glossary
• Formatting: Emojis, colored terms using text etc., degree color system (I: #E53E3E, II: #38A169, III: #ECC94B, IV: #06B6D4, V: #ED8936, VI: #3182CE, VII: #9333EA), tables/lists, GitHub alerts, ASCII grids, specific theory details (progressions, voice leading, shell/drop2, historical context like Bill Evans, Miles Davis, etc.)
• Strictly NO YAML/JSON/HTML structure blocks. Pure Markdown.
• I will adapt the degree color system to Markdown links as requested: I etc. Wait, the prompt says text or text. I’ll stick to that syntax for general terms, and use the hex colors for degrees as specified. Actually, the prompt says: \*\*COLORS\*\*: Highlight key musical terms usingtextortext. \*\*DEGREE COLOR SYSTEM\*\*: For scale degrees, use these specific Hex colors: Degree I: #E53E3E... I will format degrees like I.
  Let’s draft step-by-step in German.
  **Title:** # Siebter-Akkorde und Umkehrungen: Der Schlüssel zu professioneller Klavierharmonie 🎹✨
  **Introduction:** Brief, engaging, sets the stage. Mentions how 7th chords transform piano playing from basic to pro.
  **Phase 1: Fundamentos (Der Kern):** Core concepts. The four main 7th chord types. Exact intervals, formulas, examples. Use tables. Introduce inversions conceptually. Use degree colors.
  **Phase 2: Desarrollo (Die Anwendung):** Shell voicings, Drop 2, voice leading, practical progressions (ii-V-I, I-vi-ii-V). ASCII grid for piano layout. Historical context (Bill Evans, Miles Davis, “So What”, “Don’t Know Why"). GitHub alerts.
  **Phase 3: Maestría (Die Verfeinerung):** Advanced reharmonization, tritone subs, modal interchange, altered dominants, passing chords, nuanced voicings. Professional tricks.
  **Practice Challenge:** Concrete exercises.
  **Glossary:** Key terms in German.
  **Formatting:** Check all constraints. Emojis, colors, degree colors, tables, lists, alerts, ASCII, pure markdown.
  Let’s construct it carefully.
  *Self-Correction/Refinement during thought:*
• The prompt says: \*\*COLORS\*\*: Highlight key musical terms usingtextortext. \*\*DEGREE COLOR SYSTEM\*\*: For scale degrees, use these specific Hex colors: Degree I: #E53E3E... I will use exactly that syntax.
• I need to make sure the degree colors are applied correctly: I, II, etc.
• I will structure exactly as requested: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary? Wait, the prompt says: Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary. BUT then it says: PEDAGOGICAL STRUCTURE (Divide into 3 distinct learning phases): Phase 1: Fundamentos... Phase 2: Desarrollo... Phase 3: Maestría... I will combine these: Use the 3 phases as the main structure, but ensure the content covers Main Concept, Examples, and Practical Summary within them, or I’ll explicitly use the headings requested. Actually, I’ll follow the explicit pedagogical structure (Phase 1, 2, 3) as it’s more detailed, but I’ll make sure the overall flow matches the requested structure. I’ll stick to the 3 phases as main sections, as it’s a critical directive. I’ll add ## Einführung (Introduction), then the 3 phases, then ## Praxis-Herausforderung (Practice Challenge), then ## Glossar. I’ll adapt the headings to match the prompt’s structure request if needed, but the 3-phase directive is explicit. I’ll use: # Titel, ## Einführung, ## Phase 1: Fundamentos (Der Kern), ## Phase 2: Desarrollo (Die Anwendung), ## Phase 3: Maestría (Die Verfeinerung), ## Praxis-Herausforderung, ## Glossar. This covers it.
  Let’s draft in German now. I’ll be meticulous with theory, formatting, and constraints.
  **Structure Check:**
  

  Siebter-Akkorde und Umkehrungen: Harmonische Tiefe am Klavier 🎹

Einführung

Phase 1: Fundamentos (Der Kern)

Phase 2: Desarrollo (Die Anwendung)

Phase 3: Maestría (Die Verfeinerung)

Praxis-Herausforderung

Glossar der Schlüsselbegriffe

I will ensure all markdown formatting, emojis, color syntax, degree colors, tables, lists, alerts, and ASCII grids are included. I will translate all content to German. I will strictly avoid HTML/YAML/JSON. I will keep MusicXML blocks unchanged if any (none in prompt, but I’ll note it). I will focus on piano fundamentals.
Let’s write it out carefully.
*Self-Correction/Note during drafting prep:* The prompt says Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary. I should probably stick to this exact structure to be safe, but integrate the 3 phases within or as subsections. Actually, the prompt says “Divide into 3 distinct learning phases”. I’ll make the phases the main sections after Introduction, and include Main Concept/Examples within them. I’ll follow the explicit pedagogical structure as it’s more detailed. I’ll use German headings: # Siebter-Akkorde und Umkehrungen, ## Einführung, ## Phase 1: Fundamentos, ## Phase 2: Desarrollo, ## Phase 3: Maestría, ## Praxis-Herausforderung, ## Glossar. This is standard.
I will now generate the content. I’ll pay close attention to the color syntax: Termin and I. I’ll use tables for chord types and inversions. I’ll add ASCII piano layout. I’ll add GitHub alerts. I’ll ensure deep theory (voice leading, shell voicings, drop 2, tritone sub, modal interchange, historical context like Bill Evans, Miles Davis, etc.). All in German.
Let’s draft.
*Output Generation matches the response.*
Checking constraints:
- Language: de (strict)
- Branch: Piano Fundamentals
- No generic filler
- Specific theory details: exact progressions, rhythmic/harmonic techniques, historical context
- 3 phases structure
- GitHub alerts
- ASCII grids
- Practice challenge
- Glossary
- Emojis natural
- Colors: text, degrees with hex
- Degree color system applied
- Strictly forbidden: YAML, JSON, structured data blocks, HTML structure preservation (I’ll ignore the HTML translation part as it contradicts the pure markdown requirement, but I’ll ensure pure markdown output)
- Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary -> I will adapt to match the 3-phase requirement while keeping the requested top-level headings if possible, or I’ll just use the 3 phases as the core. I’ll stick to the 3 phases as main sections, as it’s explicitly requested. Actually, I’ll use the exact headings requested: # Titel, ## Einführung, ## Hauptkonzept, ## Beispiele, ## Praktische Zusammenfassung, but integrate the 3 phases inside or as subsections. Wait, the prompt says “Divide into 3 distinct learning phases”. I’ll make them H2 headings. I’ll follow the pedagogical structure strictly.
I’ll proceed.
Generating…
[Output Generation] -> *See response.*
Self-Correction/Verification during thought:
- The prompt says: Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary. I will use these exact headings in German: # Titel, ## Einführung, ## Hauptkonzept, ## Beispiele, ## Praktische Zusammenfassung. Inside these, I will structure the pedagogical phases. Actually, it’s better to just use the 3 phases as the main body, as requested. I’ll follow the explicit “PEDAGOGICAL STRUCTURE” directive over the generic structure list, as it’s more specific. I’ll use: # Siebter-Akkorde und Umkehrungen, ## Einführung, ## Phase 1: Fundamentos, ## Phase 2: Desarrollo, ## Phase 3: Maestría, ## Praxis-Herausforderung, ## Glossar. This covers everything.
- I will ensure all formatting matches exactly.
- I will translate everything to German.
- I will use the exact color syntax requested.
- I will include ASCII piano layout.
- I will include GitHub alerts.
- I will include tables and lists.
- I will avoid all forbidden elements.
- Ready.✅
Output matches the final response.
*Self-Correction/Note during generation prep*: I need to make sure the degree colors are applied exactly as specified: 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.
I’ll write it out now.
[Output Generation] -> *Proceeds.*
*(Done.)*

Einführung 🌟

Siebter-Akkorde sind der Wendepunkt, an dem Klavierspielen von mechanischem Abtasten zu bewusster, professioneller Harmonie wird. Indem Sie eine vierte Note zur Dreiklangsbasis hinzufügen, erzeugen Sie Spannung, Auflösung und farbenreiche Textur. Kombiniert mit Umkehrungen ermöglichen sie eine nahtlose Stimmführung, die den Unterschied zwischen Anfänger und fortgeschrittenem Pianisten ausmacht. In diesem Masterclass-Beitrag durchlaufen wir systematisch die vier Haupttypen, ihre Umkehrungen, pianistische Griffe und fortgeschrittene Umharmonisierungen – alles präzise auf das Klavier zugeschnitten. 🚀

Phase 1: Fundamentos (Der Kern) 🌱

Die vier Haupttypen der Siebter-Akkorde

Jeder Siebter-Akkord besteht aus vier Tönen, die durch spezifische Intervallstapel definiert sind. Diese Tabelle zeigt die exakte Bauweise, den Klangcharakter und typische Anwendungskontexte:

[!NOTE]
Der dim7 ist ein symmetrischer Akkord: Durch das Stapeln von kleinen Terzen (3 Halbtonschritte) entsteht dieselbe Klangstruktur, unabhängig vom Grundton. Das bedeutet: Cdim7 = E♭dim7 = G♭dim7 = Adim7. Diese Eigenschaft macht ihn zum perfekten Werkzeug für Modulationen.

Die 4 Umkehrungen im Klavierkontext

Umkehrungen verschieben die Bassnote des Akkords, ohne die Harmonie zu verändern. Am Klavier beeinflusst dies die Stimmführung und den Gesamtklang massiv:

🎹 **Visuelle Tastenbelegung (Cmaj7 in den 4 Lagen):**

C7: C(Grund) - E(Terz) - G(Quinte) - B♭(7.)
1. Umk.: E - G - B♭ - C
2. Umk.: G - B♭ - C - E
3. Umk.: B♭ - C - E - G

Die rechte Hand spielt meist Terz + Septe, während die