1. **Analyze User Input:**

• **Role:** World-Class Musicologist, Lead Music Educator, Master Arranger/Producer.
• **Task:** Write a comprehensive masterclass post about “Counterpoint and Harmonic Counterpoint”.
• **Language:** STRICTLY de (German).
• **Branch/Category:** Songwriting and Composition.
• **Critical Directives:**
• NO generic filler.
• PROVIDE SPECIFIC, CONCRETE MUSIC THEORY DETAILS: Exact chord progressions, rhythmic breakdown, harmonic/melodic techniques, historical context, key artists/recordings.
• PEDAGOGICAL STRUCTURE: 3 phases (Fundamentos, Desarrollo, Maestría).
• FORMATTING: GitHub-flavored Markdown, alerts (> [!NOTE], etc.), ASCII rhythm grids/chord boxes, Practice Challenge, Key Terms Glossary.
• EMOJIS: Use naturally.
• COLORS: Highlight key terms with text or text. Use specific Hex colors for scale degrees (I: #E53E3E, II: #38A169, III: #ECC94B, IV: #06B6D4, V: #ED8936, VI: #3182CE, VII: #9333EA). *Wait, the prompt says text but also specifies Hex colors for degrees. I’ll use the exact format requested: text for general terms, and for degrees I’ll use I etc., or adapt to the requested syntax. The prompt says: Highlight key musical terms using text or text. DEGREE COLOR SYSTEM: For scale degrees, use these specific Hex colors: Degree I: #E53E3E... I will follow this strictly.*
• DIDACTIC TOOLS: Markdown Tables and Lists.
• STRICTLY FORBIDDEN: YAML, JSON, structured data blocks. Pure Markdown.
• Structure requested in prompt: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary. BUT later it says PEDAGOGICAL STRUCTURE (Divide into 3 distinct learning phases): Phase 1: Fundamentos, Phase 2: Desarrollo, Phase 3: Maestría. I will adapt the structure to match the pedagogical phases while keeping the requested flow, or explicitly use the phases as main sections. I’ll stick to the 3-phase structure as it’s a critical directive.
• **ADDITIONAL INSTRUCTIONS (CRITICAL):** The prompt ends with a very specific instruction about HTML translation: “The post.content field contains HTML with music theory content. 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 contradictory. The main prompt asks for a Markdown masterclass post. The “ADDITIONAL INSTRUCTIONS” at the end sound like a template from a different system that expects HTML output. However, the user explicitly says: “Now, write the complete, expert-level masterclass post in Markdown format:” and then lists the ADDITIONAL INSTRUCTIONS which seem to be copied from a different prompt context ("The post.content field contains HTML…"). I need to reconcile this. The safest approach is to output **pure Markdown** as requested in the main prompt, but incorporate the translation requirement (German language) and the pedagogical structure. I will ignore the HTML-specific constraints if they conflict with the “pure Markdown” and “masterclass post” request, but I will strictly follow the German language requirement, the 3-phase structure, the specific formatting (alerts, ASCII, glossary, emojis, colors), and the detailed music theory requirements. Actually, the prompt says “Translate ONLY the visible text content to de while preserving the exact HTML structure…”. This is a common prompt injection/template mismatch. I will prioritize the main explicit instructions: German language, Markdown format, 3-phase structure, specific theory details, emojis, colors, alerts, ASCII, glossary, practice challenge. I will NOT output HTML unless explicitly forced, but the prompt says “Return the translated HTML content with the title translated.” This is tricky. I’ll stick to Markdown as the primary format requested ("write the complete, expert-level masterclass post in Markdown format"), but I’ll make sure it’s in German. I will ignore the HTML preservation instruction as it contradicts “MUST be pure Markdown” and “write… in Markdown format”. I’ll focus on delivering a high-quality German Markdown masterclass.
  Let’s carefully map out the content in German:
• Title: Kontrapunkt und Harmonischer Kontrapunkt
• Language: German
• Structure:
  

  Kontrapunkt und Harmonischer Kontrapunkt

Einführung

Phase 1: Fundamentos (Der Samen)

Phase 2: Desarrollo (Das Wachstum)

Phase 3: Maestría (Die Blüte)

Praxis-Herausforderung / Reto Práctico

Glossar der Schlüsselbegriffe

• I need to integrate the specific requirements:
• Emojis naturally
• Colors for terms: Kontrapunkt, Stimmführung, etc.
• Degree colors: I, II, etc.
• GitHub alerts: > [!NOTE], > [!TIP], > [!IMPORTANT]
• ASCII rhythm grids/chord boxes
• Exact chord progressions, rhythmic breakdowns, harmonic/melodic techniques, historical context, key artists
• Tables and lists
• No YAML/JSON
• Pure Markdown
  Let’s draft step-by-step in German.
  **Title:** # Kontrapunkt und Harmonischer Kontrapunkt 🎵
  **Introduction:** Brief, engaging, sets the stage. Explain that counterpoint isn’t just Baroque theory, but a vital tool for modern songwriting. Use Kontrapunkt.
  **Phase 1: Fundamentos (Der Samen) 🌱**
• Core rhythmic pattern & foundational harmony.
• Explain the 4 motions: Gleichgerichtete Bewegung, Ähnliche Bewegung, Gegensatzbewegung, Schiefe Bewegung.
• Use a table for motions.
• Introduce basic harmonic counterpoint: bass vs melody.
• Historical context: Palestrina, Bach, but pivot quickly to modern application (Beatles, Radiohead, Radiohead’s “Creep” or “Karma Police”, or modern pop like Billie Eilish, Finneas).
• Rhythmic breakdown: 4/4 time, syncopation, accent placement. ASCII grid for a basic contrapuntal rhythm pattern.
• Alert: > [!NOTE]
  **Phase 2: Desarrollo (Das Wachstum) 🌿**
• Practical applications, chord voicings, piano/guitar patterns.
• Voice leading (Stimmführung): stepwise motion, common tones, contrary outer voices, tendency tones (VII -> I, IV -> III).
• Apply degree colors: VII resolves to I, IV resolves to III.
• Chord progressions: ii7 - V7 - Imaj7, I - vi - ii - V7, tritone subs, extended chords (Cmaj9, D9, F#m7b5).
• Explain how to weave counterpoint into these.
• ASCII chord box or piano pattern.
• Alert: > [!TIP]
  **Phase 3: Maestría (Die Blüte) 🌸**
• Advanced reharmonizations, professional tricks, improvisation.
• Modal interchange, altered scales, anticipatory bass.
• Rhythmic counterpoint: polyrhythms, clave patterns (2-3 vs 3-2), syncopation.
• Historical/Modern pioneers: Bach, but also Billie Holiday, Dolly Parton, modern producers like Jack Antonoff, Daniel Lopatin (Oneohtrix Point Never), or film composers like Hildur Guðnadóttir. Let’s stick to songwriting: The Beatles ("Nowhere Man"), Radiohead, Finneas/Billie Eilish, Taylor Swift ("All Too Well").
• Alert: > [!IMPORTANT]
  **Praxis-Herausforderung / Reto Práctico 🎹**
• Step-by-step exercise.
  **Glossar der Schlüsselbegriffe 📖**
• Table or list.
  Now, I will write it out carefully in German, ensuring all constraints are met. I’ll pay close attention to the color syntax and degree colors. I’ll make sure the markdown is pure. I’ll incorporate the ASCII grids and alerts. I’ll avoid filler. I’ll focus on concrete theory.
  Let’s draft mentally first, then generate.
  *Self-Correction/Refinement during thought:*
• The prompt says: “Highlight key musical terms using text or text.” I will use exactly that syntax.
• Degree colors: Degree I: #E53E3E etc. I will format them as I.
• The prompt 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_1__… STRICTLY FORBIDDEN: Do NOT generate or mention ‘MusicXML’… Return the translated HTML content with the title translated.”
• This is a conflicting instruction. The main prompt says “write the complete, expert-level masterclass post in Markdown format”. The additional instructions seem to be a copy-paste error from a different task. I will prioritize the explicit “Markdown format” and “3-phase structure” and “German language” instructions. I will output pure Markdown as requested. If the system actually wants HTML, it would have said “Output HTML”. I’ll stick to Markdown. I will ignore the HTML preservation part as it contradicts “MUST be pure Markdown” and “write… in Markdown format”. I’ll proceed with Markdown.
  Structure:
  

Einführung

Phase 1: Fundamentos (Der Samen) 🌱

Phase 2: Desarrollo (Das Wachstum) 🌿

Phase 3: Maestría (Die Blüte) 🌸

Praxis-Herausforderung / Reto Práctico 🎹

Glossar der Schlüsselbegriffe 📖

I will now generate the content in German, carefully applying all constraints.
- Emojis: 🎵, 🎹, 💡, 😂, 🚀, 🌱, 🌿, 🌸, etc.
- Colors: Kontrapunkt, Stimmführung, etc.
- Degrees: I, II, III, IV, V, VI, VII
- Alerts: > [!NOTE], > [!TIP], > [!IMPORTANT]
- ASCII grids for rhythm/chords
- Tables for motions, glossary
- Specific theory: exact progressions, voice leading rules, historical/modern examples, rhythmic breakdown.
- Language: German.
- No filler.
- Pure Markdown.
Let’s write it out.
I’ll make sure the German is professional and musically accurate.
I’ll structure the content carefully.
I’ll check all constraints.
Ready.✅
Generating.
*Self-Correction/Note during drafting mental:*
The prompt says “Highlight key musical terms using text or text.” and “DEGREE COLOR SYSTEM: For scale degrees, use these specific Hex colors: Degree I: #E53E3E…”. I will apply these exactly.
I will use GitHub-flavored markdown.
I will ensure the 3 phases are clearly marked.
I will include the ASCII rhythm grid and chord box.
I will include the alerts.
I will keep it concise but thorough.
All good.
Output matches the response.
Proceeds.
[Output Generation] -> *See response.*
*Check against constraints:*
- Language: de ✅
- Branch: Songwriting and Composition ✅
- No generic filler ✅
- Specific theory details ✅
- 3 phases ✅
- GitHub alerts ✅
- ASCII grids/boxes ✅
- Practice challenge ✅
- Glossary ✅
- Emojis ✅
- Colors & Degree system ✅
- Tables & Lists ✅
- Pure Markdown ✅
- Structure matches request ✅
- HTML instruction ignored as it contradicts “MUST be pure Markdown” and “write… in Markdown format”. I will output pure Markdown as instructed in the main body. If the system strictly wants HTML, it’s a prompt conflict, but I’ll follow the explicit “Markdown format” directive. Actually, I’ll just output Markdown. The prompt says “Now, write the complete, expert-level masterclass post in Markdown format:”. I’ll stick to that.
All set.
Generating.
*[Output Generation]* (matches the final response)
*Self-Correction/Verification during thought:*
Wait, the prompt 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…”. This is a very specific instruction that might override the markdown request. But it also says “STRICTLY FORBIDDEN: Do NOT use YAML format, JSON format, or any structured data block. The output MUST be pure Markdown.” These are contradictory. I will prioritize the “pure Markdown” and “masterclass post” instructions, as they are more detailed and specific to the task. I will output Markdown. If the user meant to paste HTML, they didn’t. I’ll proceed with Markdown.
I’ll make sure the German is flawless and the music theory is expert-level.
All constraints met. Output matches response.
Proceeds.
[Output Generation] -> *See response.*
*(Done.)*

Einführung

Kontrapunkt ist die Kunst, unabhängige Melodielinien zu einem kohärenten harmonischen Ganzen zu verschmelzen. Während sich das moderne Songwriting oft auf „Melodie plus Begleitung“ konzentriert, fügt der Kontrapunkt eine Ebene der Raffinesse hinzu, bei der mehrere Stimmen zwar eigenständig verlaufen, aber gemeinsam etwas Größeres erschaffen. Es ist der Unterschied zwischen einer Monologe und einem lebendigen musikalischen Dialog 🗣️🎶.
Historisch gesehen reicht die Tradition von den polyphonen Chören der Renaissance über die streng durchkomponierten Fugen J.S. Bachs bis hin zu den durchdachten Keyboard-Layers von Brian Eno oder den rhythmisch versetzten Basslinien von Finneas. In der modernen Komposition ist Kontrapunkt weniger ein starres Regelwerk als vielmehr ein Werkzeug zur Schaffung von Tiefe, Spannung und melodischer Autonomie.

[!NOTE]

> Kontrapunkt bedeutet nicht „kompliziert“. Es bedeutet „zusammenklingend“. Jede Linie muss für sich genommen singbar und interessant sein, bevor sie mit anderen verwebt wird.

Phase 1: Fundamentos (Der Samen) 🌱

Kern-Rhythmus & Grundharmonie

Der harmonische Kontrapunkt beginnt mit der rhythmischen Unabhängigkeit der Stimmen. In einem Standard-4/4-Takt entsteht Kontrapunkt oft durch **rhythmische Verschiebung** und **Akzentverteilung**.
**ASCII-Rhythmusgitter: Melodie vs. Bass (4/4)**

Takt 1 | 1 & 2 & 3 & 4 &
Mel | X . . X . . . X . . . X . .
Bass | . X . . X . . . X . . . X .

*Die Melodie beginnt auf der Zählzeit, der Bass antwortet auf die „&“. Diese Synkopierung erzeugt sofort Bewegung und verhindert, dass beide Stimmen im Gleichtakt „klatschen“.*

Die vier Bewegungsarten

Jede kontrapunktische Beziehung lässt sich in eine der vier Grundbewegungen einordnen: