1. **Analyze User Input:**

• **Role:** World-Class Musicologist, Lead Music Educator, Master Arranger/Producer.
• **Task:** Write a comprehensive, deeply informative, engaging masterclass post about a musical topic/style.
• **Language:** STRICTLY German (de).
• **Branch/Category:** Guitar Fundamentals.
• **Critical Directives:**
• NO generic/filler text.
• 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: Clean GitHub-flavored Markdown, GitHub alerts (> [!NOTE], etc.), ASCII rhythm grids/chord boxes, “Practice Challenge / Reto Práctico” section, Key Terms Glossary at the end.
• **ADDITIONAL INSTRUCTIONS (CRITICAL):** 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… PRESERVE ALL PLACEHOLDER MARKERS like __MUSICXML_BLOCK_0__ EXACTLY AS THEY APPEAR… STRICTLY FORBIDDEN: Do NOT generate or mention ‘MusicXML’… STRICTLY FORBIDDEN: Do NOT add any explanations, comments, or text outside the original HTML content… Return the translated HTML content with the title translated.”
• Wait, there’s a contradiction/conflict here. The initial prompt asks for a Markdown masterclass post with specific structure, emojis, degree colors, didactic tools, etc. But the final “ADDITIONAL INSTRUCTIONS” say: “The post.content field contains HTML… Translate ONLY the visible text content to de while preserving the exact HTML structure… STRICTLY FORBIDDEN: Do NOT add any explanations, comments, or text outside the original HTML content.”
• This is a common prompt injection/conflict scenario. I need to carefully reconcile these. The user provided an “ORIGINAL DRAFT/TOPIC TO ENRICH & TRANSFORM” in Markdown. The final instruction says “Translate ONLY the visible text content to de while preserving the exact HTML structure… Return the translated HTML content with the title translated.” But the original draft is in Markdown, not HTML. And the prompt says “The post.content field contains HTML…”. This is likely a template mismatch.
• I will prioritize the main structural and formatting instructions (Markdown, 3 phases, German, specific theory details, emojis, colors, tables, alerts, practice challenge, glossary) while acknowledging the final instruction’s demand for German and preserving any placeholders if they existed (none exist in the draft, but I’ll keep the structure). Actually, the final instruction seems to be a copy-paste from a translation task, but the main prompt is clearly asking for a masterclass post in Markdown. I will follow the main prompt’s structure and formatting requirements, write it in German, and ensure it’s a comprehensive masterclass on Power Chords for Guitar Fundamentals. I will ignore the contradictory HTML translation instruction because the input is Markdown, and the main prompt explicitly says “create clear, focused, educational content in Markdown format” and gives a detailed structure. I’ll adapt the final instruction’s spirit (German language, precise terminology) into the Markdown output.
• Let’s carefully map out the requirements:
• Language: German (de)
• Topic: Power Chords (Guitar Fundamentals)
• Structure: # Title, ## Introduction, ## Main Concept (split into Phase 1, 2, 3), ## Examples, ## Practical Summary (or adapt to the 3-phase structure requested)
• Actually, the prompt says: “Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary.” AND “PEDAGOGICAL STRUCTURE (Divide into 3 distinct learning phases): Phase 1: Fundamentos, Phase 2: Desarrollo, Phase 3: Maestría”. I will combine these logically.
• Use emojis naturally.
• Color key terms: text, text.
• Degree color system: Not heavily applicable to power chords (which are just I, IV, V usually), but I’ll use them for scale degrees if mentioned (e.g., I, IV, V).
• Didactic tools: Markdown tables and lists.
• GitHub alerts: > [!NOTE], > [!TIP], > [!IMPORTANT].
• ASCII rhythm grids/chord boxes.
• Practice Challenge section.
• Key Terms Glossary.
• NO YAML/JSON/structured data blocks. Pure Markdown.
• Focus on ONE main concept: Power Chords.
• Provide specific theory: exact progressions, rhythmic breakdown, harmonic/melodic techniques, historical context, key artists.
• Write in German.

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

• **Title:** Power Chords: Das fundamentale Rückgrat der Rockgitarre
• **Introduction:** Define power chords technically (Root + 5th, optional octave). Explain why they work (no 3rd = major/minor ambiguity, perfect for distortion). Historical context (early rock, punk, metal). Key artists: James Hetfield, Joe Elliott (wait, vocals), Tom Morello, Jimmy Page, Kurt Cobain. Landmark recordings: “Back in Black”, “Nevermind”, “Appetite for Destruction”.
• **Phase 1: Fundamentos (The Seed):** Core shape, fretboard mapping, finger placement, muting techniques (palm muting, fret-hand muting). Rhythmic foundation: straight 8th notes, syncopation, downpicks vs alternate. ASCII chord box. Table of fret positions.
• **Phase 2: Desarrollo (The Growth):** Progressions (I-IV-V, I-vi-iv-V adapted for power chords), rhythmic variations (16th notes, triplets, accent placement), strumming patterns, bassline integration. Voice leading concepts (moving 5ths vs octaves). ASCII rhythm grid.
• **Phase 3: Maestría (The Flower):** Advanced techniques: adding the 4th/11th, suspended power chords, chromatic passing chords, double-stop bends, whammy bar techniques, tone shaping (EQ for power chords), rhythmic displacement. Reharmonization concepts in rock context.
• **Examples:** Concrete chord progressions with exact fret numbers, rhythmic notation in ASCII, tempo/BPM suggestions.
• **Practice Challenge / Reto Práctico:** Specific drill with BPM, progression, muting, and rhythmic variation.
• **Key Terms Glossary:** German terms with explanations.
• **Formatting:** Emojis, colors, tables, alerts, degree colors where applicable.
  Let’s draft carefully, ensuring all constraints are met.
  *Self-Correction/Refinement during planning:*
• The prompt says: “Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary.” AND “PEDAGOGICAL STRUCTURE (Divide into 3 distinct learning phases)…”. I will structure it as:
  

  Title

Introduction

Main Concept

Phase 1: Fundamentos (Der Keim)

Phase 2: Desarrollo (Das Wachstum)

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

Examples

Practical Summary

(Plus Practice Challenge & Glossary at the end, as requested)
- I need to use the exact degree color system: Degree I: #E53E3E, etc. I’ll apply it to scale degrees in progressions.
- I need to use text and text for key terms.
- I need GitHub alerts.
- I need ASCII grids/boxes.
- I need to write strictly in German.
- I must avoid generic filler. Provide exact theory.
- I will carefully craft the content now.
Structure check:

Introduction

Main Concept

Phase 1: Fundamentos (Der Keim)

Phase 2: Desarrollo (Das Wachstum)

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

Examples

Practical Summary

[!NOTE], > [!TIP], > [!IMPORTANT] integrated.
ASCII chord box & rhythm grid.
Practice Challenge / Reto Práctico.
Key Terms Glossary.
All in German. Pure Markdown. No YAML/JSON. Degree colors applied. Key term colors applied.
Let’s write it out carefully.
I will ensure the degree colors are applied exactly as hex codes in the markdown link syntax or inline if supported, but the prompt says: Degree I: #E53E3E, Degree II: #38A169... I’ll use them like [I](#E53E3E) or just apply the hex in the text if possible. The prompt says: “For scale degrees, use these specific Hex colors: Degree I: #E53E3E…”. I’ll format them as [I](#E53E3E) or just use inline HTML I? The prompt says “use these specific Hex colors”, I’ll stick to markdown links or direct hex in text. Actually, standard markdown doesn’t support hex colors in links like that unless it’s a specific platform. I’ll use [I](#E53E3E) as requested, or just apply the hex directly if the platform supports it. I’ll follow the prompt literally: Degree I: #E53E3E -> I’ll write [I](#E53E3E) or just use the hex in a markdown format. I’ll use [I](#E53E3E) as a placeholder for the color system, or better, just use the hex directly in inline CSS if allowed, but to be safe with “pure Markdown”, I’ll use [I](#E53E3E) or just write it out. Actually, many AI prompts expect [I](#E53E3E) or similar. I’ll stick to [I](#E53E3E) format. Wait, 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 format degrees as [I](#E53E3E), [IV](#06B6D4), [V](#ED8936).
Let’s draft carefully.
I will make sure every constraint is met.
- Language: German
- Structure: # Title, ## Introduction, ## Main Concept (with 3 phases), ## Examples, ## Practical Summary
- Emojis: 🎸, 🎵, 💡, 🚀, etc.
- Colors: text, text, degrees with hex.
- Tables & Lists: Yes.
- Alerts: Yes.
- ASCII: Yes.
- Practice Challenge & Glossary: Yes.
- Theory: Exact progressions, rhythms, muting, historical context, artists.
- No filler.
- Pure Markdown.
Draft generation starts now.
I’ll carefully construct each section.
*Self-Correction/Verification during thought:*
- The prompt says “Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary.” I will follow this exactly.
- I will embed the 3 phases under “## Main Concept” or as subsections.
- I will ensure the German is precise and musical.
- I will check the degree color format. I’ll use [I](#E53E3E) etc.
- I will add the ASCII chord box and rhythm grid.
- I will add the GitHub alerts.
- I will add the Practice Challenge and Glossary.
- All constraints met. Proceed.
Output matches the response.
Generating…
[Output Generation] -> *Proceeds to write the full German markdown response.*
*Check during generation:*
- “Power Chords: Das fundamentale Rückgrat der Rockgitarre"
- Intro: Technical definition, historical context (early rock, punk, metal), artists (Hetfield, Cobain, Page, Osbourne), recordings.
- Main Concept: Phase 1 (Shape, muting, fretboard map), Phase 2 (Progressions, rhythm, voice leading), Phase 3 (Extensions, chromaticism, tone shaping).
- Examples: Exact progressions with fret numbers, ASCII rhythm grid.
- Practical Summary: Concise recap.
- Alerts: Integrated naturally.
- Tables/Lists: Used for fret map, rhythm breakdown, glossary.
- Colors: Applied as requested.
- Language: Strictly German.
- Format: Pure Markdown.
All good. Output matches.
*Self-Correction/Note during thought*: The prompt says “Highlight key musical terms using text or text.” I will use exactly that syntax. For degrees, I will use [I](#E53E3E) etc. as specified. I’ll make sure the markdown is clean. I will avoid any HTML except if necessary for the degree colors, but I’ll stick to the requested syntax. Actually, to be safe with the hex colors, I’ll use [I](#E53E3E) as requested. Some platforms render this as a link, but it’s what’s asked. Alternatively, I can just write I (#E53E3E) but the prompt says “use these specific Hex colors”. I’ll stick to [I](#E53E3E).
Let’s produce the response.
Structure:

Power Chords: Das fundamentale Rückgrat der Rockgitarre 🎸

Introduction

Main Concept

Phase 1: Fundamentos (Der Keim)

Phase 2: Desarrollo (Das Wachstum)

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

Examples

Practical Summary

[!NOTE] …
[!TIP] …
[!IMPORTANT] …
Practice Challenge / Reto Práctico
Key Terms Glossary
All in German. Pure Markdown. No extra text. Ready.
Output generation.
*[Proceeds]*

Power Chords: Das fundamentale Rückgrat der Rockgitarre 🎸

Introduction

Power Chords sind die harmonische und rhythmische Triebkraft von Rock, Punk, Hard Rock und Metal. Technisch gesehen sind sie keine vollständigen Dreiklänge, sondern bestehen ausschließlich aus der Grundtonlage und der Quinte – optional verdoppelt in der Oktave. Diese bewusste Auslassung der Terz eliminiert die Dur/Moll-Ambivalenz und verhindert schmutzige, dissonante Obertöne bei hoher Verzerrung.
Historisch gesehen wurden Power Chords in den 1960er Jahren durch Gitarristen wie Jimmy Page und Barry Gibb populär, fanden aber in den 1970er/80er Jahren durch Ozzy Osbourne/Randy Rhoads und AC/DC ihre tonale Reife. Die 1990er Jahre (Grunge & Alternative Rock) perfektionierten ihre rhythmische Anwendung. Landmark-Alben wie *„Nevermind“* (Nirvana), *„Appetite for Destruction“* (Guns N’ Roses) und *„Back in Black“* (AC/DC) demonstrieren, wie reduzierte Harmonik maximale rhythmische Kraft entfesselt.

Main Concept

Phase 1: Fundamentos (Der Keim) 🌱

Das Grundgerüst eines Power Chords basiert auf zwei festen Fingern. Die Form ist vollständig verschiebbar und unabhängig von der Lage auf dem Griffbrett.
**Standard-Griff (Saite 6 als Grundton):**

e |---|
B |---|
G |---|
D |-5-| ← 3. Finger (Quinte)
A |-3-| ← 1. Finger (Grundton)
E |-3-| ← 4. Finger (Oktave, optional)
3

[!NOTE]
Die Oktave (4. Finger) ist optional. In schnellen Tempi (>140 BPM) wird sie oft weggelassen, um Saitenwechsel zu beschleunigen.
**Stummschaltung (Muting) – Das technische Fundament:**
Unkontrollierte Saitenschwebungen zerstören den klaren Punch von Power Chords. Zwei Techniken sind obligatorisch:
1. **Palm Muting:** Die Kante der Zupfhand ruht minimal auf den Saiten nahe dem Steg. Dies erzeugt den charakteristischen chunky, percussive chug.
2. **Fret-Hand Muting:** Der Zeigefinger berührt leicht die höheren Saiten (B & e), während der Ringfinger die Quinte hält. Dies tötet unerwünschte Obertöne sofort ab.
**Griffb