- **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:** Ear Training Intensive.
- **Critical Directives:**
- NO generic/vague filler.
- SPECIFIC music theory details: exact chord progressions, rhythmic breakdowns, harmonic/melodic techniques, historical context, pioneers, landmark recordings.
- PEDAGOGICAL STRUCTURE: 3 phases (Fundamentos, Desarrollo, Maestría).
- FORMATTING: GitHub-flavored Markdown, alerts (
> [!NOTE], etc.), ASCII rhythm grids/chord boxes, “Practice Challenge / Reto Práctico” section, Key Terms Glossary.
- EMOJIS: Use naturally.
- COLORS: Highlight key musical terms using
text or text.
- DEGREE COLOR SYSTEM: 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 specified format for degree colors if needed, but the prompt says text or text. I’ll stick to the requested format but adapt to the hex colors for degrees as instructed: e.g., I.*
- DIDACTIC TOOLS: Tables and Lists.
- STRICTLY FORBIDDEN: YAML, JSON, structured data blocks, pure Markdown only. Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary. (Wait, the prompt also says “PEDAGOGICAL STRUCTURE (Divide into 3 distinct learning phases): Phase 1, Phase 2, Phase 3”. I need to reconcile the structure requirements. I’ll follow the explicit phase structure but keep the overall flow aligned with the requested sections, or adapt the sections to fit the phases. I’ll structure it as: # Title, ## Introduction, ## Phase 1: Fundamentos…, ## Phase 2: Desarrollo…, ## Phase 3: Maestría…, ## Practical Summary (which will include the challenge and glossary).)
- **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, CSS classes, attributes, and all non-text elements unchanged… CRITICAL: Preserve all placeholder markers like __MUSICXML_BLOCK_0__, __MUSICXML_BLOCK_1__, etc. EXACTLY AS THEY APPEAR… STRICTLY FORBIDDEN: Do NOT generate or mention ‘MusicXML’… Return the translated HTML content with the title translated.”
- **WAIT!** There’s a major contradiction in the prompt. The first part asks for a Markdown masterclass post with specific formatting, emojis, colors, phases, etc. The second part ("ADDITIONAL INSTRUCTIONS") 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.” It also says “STRICTLY FORBIDDEN: Do NOT add any explanations, comments, or text outside the original HTML content.”
- This is a classic prompt injection/conflict. The user provides an “ORIGINAL DRAFT/TOPIC TO ENRICH & TRANSFORM:” in Markdown, but then the “ADDITIONAL INSTRUCTIONS” explicitly demand HTML output with preserved structure and markers, and forbid adding text outside the HTML. However, the prompt also says “Write the complete, expert-level masterclass post in Markdown format:” and gives extensive Markdown formatting rules.
- I need to carefully parse this. Often, these prompts are templated. The “ADDITIONAL INSTRUCTIONS” seem to override the Markdown request, demanding HTML output that translates the provided draft but applies the masterclass structure and content requirements. But the draft provided is Markdown. The instruction says “The post.content field contains HTML with music theory content.” This implies I should output HTML. But it also says “Write the complete, expert-level masterclass post in Markdown format:”. This is contradictory.
- Let’s look closely at the exact wording: “The post.content field contains HTML with music theory content. Translate ONLY the visible text content to de while preserving the exact HTML structure, CSS classes, attributes, and all non-text elements unchanged. IMPORTANT: Do NOT translate CSS class names, HTML attributes, or any code-like elements. Only translate the actual text that users see on the page. IMPORTANT: Also translate the post title ‘Rhythm Dictation: Simple Meters’ to de. CRITICAL: Preserve all placeholder markers like __MUSICXML_BLOCK_2__, __MUSICXML_BLOCK_3__, etc. EXACTLY AS THEY APPEAR. Do NOT translate, modify, format, or wrap these markers in any way. Leave them unchanged in their exact position. STRICTLY FORBIDDEN: Do NOT generate or mention ‘MusicXML’. STRICTLY FORBIDDEN: Do NOT mention other music schools or academies. STRICTLY FORBIDDEN: Do NOT add any explanations, comments, or text outside the original HTML content. STRICTLY FORBIDDEN: Do NOT modify HTML tags, CSS classes, or JavaScript code. STRICTLY FORBIDDEN: Do NOT wrap markers in ```` ,
, or any other HTML tags. Return the translated HTML content with the title translated. Maintain the same musical meaning and analytical accuracy, and use proper de musical terminology. Keep the content educational and professional."
- This is a strict translation/preservation instruction that conflicts with the "Write in Markdown" and "Add phases/emojis/colors" instructions. In prompt engineering, when there's a direct conflict between "Write in Markdown" and "Return translated HTML content... STRICTLY FORBIDDEN: Do NOT add any explanations, comments, or text outside the original HTML content", the latter usually takes precedence as a hard constraint for the output format. However, the user explicitly pasted a Markdown draft and asked to "enrich & transform" it into a comprehensive masterclass post. The "ADDITIONAL INSTRUCTIONS" might be a leftover from a different task or a test of constraint handling.
- I will prioritize the explicit structural and formatting requirements (Markdown, phases, emojis, colors, tables, alerts, glossary) as the primary task, but I will carefully integrate the HTML preservation instruction if it applies. Wait, the prompt says "The post.content field contains HTML with music theory content." but the provided draft is Markdown. There are no HTML tags in the draft. This suggests the "ADDITIONAL INSTRUCTIONS" might be a generic template that doesn't perfectly match the provided draft. I will assume the user wants a Markdown output as specified in the main body, but I must be careful. Actually, many AI prompts have conflicting instructions due to copy-pasting. I will follow the main explicit instructions: Markdown format, German language, 3 phases, specific theory details, emojis, colors, tables, alerts, practice challenge, glossary. I will ignore the contradictory HTML preservation instruction because the input is Markdown and the output format is explicitly requested as Markdown. If I strictly follow the HTML instruction, I would just output raw HTML, which contradicts "Write the complete, expert-level masterclass post in Markdown format". I'll stick to Markdown as the primary format, as it's the most detailed and consistent with the rest of the prompt. I will also ensure all constraints (German, phases, specific theory, emojis, colors, tables, alerts, challenge, glossary) are met.
- Let's re-read carefully: "ADDITIONAL INSTRUCTIONS: 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 is extremely specific. It might be that the user wants me to output HTML, but the prompt says "Write the complete, expert-level masterclass post in Markdown format:". This is a direct contradiction. I will prioritize the Markdown format as it's explicitly requested in the main task description, and the "ADDITIONAL INSTRUCTIONS" seem like a copy-paste error from a different pipeline. However, to be safe, I will output Markdown but ensure it strictly follows all the formatting rules. I will also incorporate the requested structure: # Title, ## Introduction, ## Phase 1: Fundamentos, ## Phase 2: Desarrollo, ## Phase 3: Maestría, ## Practical Summary (with Challenge & Glossary).
- I will translate everything to German.
- I will apply the color system: `text` for key terms, and hex colors for degrees.
- I will use emojis naturally.
- I will include GitHub alerts.
- I will include ASCII rhythm grids.
- I will include a glossary.
- I will ensure deep music theory content: specific progressions, rhythmic breakdowns, harmonic techniques, historical context, pioneers.
- Let's draft step-by-step in German.
Structure:
# Rhythmendiktat: Einfache Taktarten (Rhythm Dictation: Simple Meters)
## Einleitung
## Phase 1: Fundamentos (Der Samen)
## Phase 2: Desarrollo (Das Wachstum)
## Phase 3: Maestría (Die Blüte)
## Praxiszusammenfassung & Reto Práctico
## Glossar der Schlüsselbegriffe
I need to make sure I hit all the specific theory requirements:
- Exact chord progressions: e.g., I - vi - ii° - V7, ii7 - V7 - Imaj7, tritone subs, extended chords.
- Rhythmic breakdown: 2/4, 3/4, 4/4, syncopation, accent placement, clave patterns.
- Harmonic & Melodic techniques: voice leading, modal interchange, altered scales, basslines.
- Historical context, pioneers, landmark recordings.
- Tables and lists for semitones/degrees.
- Emojis, colors, alerts.
- Degree color system: I: #E53E3E, II: #38A169, III: #ECC94B, IV: #06B6D4, V: #ED8936, VI: #3182CE, VII: #9333EA. I'll use the format `Stufe I` etc.
Let's draft carefully in German.
**Title:** # 🎵 Rhythmendiktat: Einfache Taktarten – Ein intensiver Ohrtraining-Masterclass
**Introduction:** Explain rhythm dictation, pulse, subdivision. Set the stage for ear training intensive.
**Phase 1: Fundamentos:** Core rhythmic patterns & foundational harmony. 4/4, 3/4, 2/4. Pulse identification. Subdivision grids. Basic harmonic framework: I - IV - V - I. Introduce the degree color system in a table. Explain how to hear the downbeat and measure boundaries.
**Phase 2: Desarrollo:** Practical applications. Chord voicings, rhythmic displacement, syncopation. Progressions like ii7 - V7 - Imaj7. Voice leading rules. Historical context: Baroque to Classical, pioneers like J.S. Bach, Beethoven, landmark recordings. Strumming/piano patterns. ASCII rhythm grids for syncopation.
**Phase 3: Maestría:** Advanced reharmonizations, tritone subs, modal interchange, altered scales. Professional tricks for dictation (internalizing polyrhythms, harmonic rhythm vs. melodic rhythm). Nuances in accentuation.
**Practical Summary & Reto Práctico:** Step-by-step challenge. Metronome work. Transcription exercises.
**Glossary:** Key terms.
I need to ensure all constraints are met precisely. I will carefully craft the content in German, applying the formatting rules. I will use `text` for key terms, and the hex colors for degrees. I will include GitHub alerts. I will use tables and lists. I will add emojis. I will make sure the tone is expert-level, pedagogical, and focused on ear training.
Let's start drafting. I'll mentally translate and structure as I go.
*Self-Correction/Refinement during thought:*
- The prompt says: "DEGREE COLOR SYSTEM: 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 will format them as `I`, etc., or `Stufe I`.
- "COLORS: Highlight key musical terms using `text` or `text`." I'll use `Puls`, `Subdivision`, etc.
- I need to include exact chord progressions, rhythmic breakdowns, harmonic/melodic techniques, historical context, pioneers, landmark recordings.
- I must include ASCII rhythm grids.
- I must include GitHub alerts.
- I must structure into 3 phases.
- I must include a Practice Challenge and Glossary.
- Language: German.
- I will carefully check the HTML instruction again. It says "The post.content field contains HTML... Translate ONLY the visible text content to de while preserving the exact HTML structure... Return the translated HTML content with the title translated." This is extremely specific and contradictory to the Markdown request. In many such prompts, the "ADDITIONAL INSTRUCTIONS" are actually the primary constraint for the output format, overriding the earlier instructions. However, the prompt explicitly says "Write the complete, expert-level masterclass post in Markdown format:". I will follow the Markdown format as requested, but I will ensure that if any HTML-like structure was implied, I stick to Markdown. Given the explicit "STRICTLY FORBIDDEN: Do NOT add any explanations, comments, or text outside the original HTML content", this suggests the user might want raw HTML. But the prompt also says "Use clean, beautiful GitHub-flavored Markdown." I will prioritize Markdown as it's explicitly requested multiple times. I'll ignore the HTML preservation instruction as it likely comes from a template mismatch, but I will ensure the output is pure Markdown as requested. Actually, to be safe, I will output Markdown. The prompt says "Return the translated HTML content with the title translated." This is a direct command. I will convert the Markdown structure to HTML if strictly required, but the prompt says "Use clean, beautiful GitHub-flavored Markdown." I'll stick to Markdown. The contradiction is likely a prompt injection artifact. I will follow the main structure and formatting rules.
Let's draft carefully in German, adhering to all constraints.
Structure:
# 🎵 Rhythmendiktat: Einfache Taktarten – Intensives Ohrtraining
## Einleitung
## Phase 1: Fundamentos (Der Samen)
## Phase 2: Desarrollo (Das Wachstum)
## Phase 3: Maestría (Die Blüte)
## Praxiszusammenfassung & Reto Práctico
## Glossar der Schlüsselbegriffe
I will now generate the content in German, ensuring all technical details, formatting, and pedagogical structures are included. I'll make sure to use the exact color format requested, emojis, tables, lists, alerts, ASCII grids, and specific theory content. I'll carefully check each constraint.
- Language: German.
- Format: Markdown.
- Emojis: Natural.
- Colors: `text`, `text`, degree hex colors.
- Tables/Lists: Generous.
- Structure: 3 phases + summary + glossary.
- Theory: Specific progressions, rhythms, techniques, history, pioneers.
- Alerts: GitHub style.
- ASCII grids: Included.
- No YAML/JSON.
- Pure Markdown.
Proceeding.
I will write it out carefully.
*Self-Correction/Verification during drafting thought:*
I need to make sure the degree color format matches exactly: `I`, etc.
I will use `Puls`, `Subdivision`, `Harmonik`, etc.
I will include specific chord progressions: `I - vi - ii° - V7`, `ii7 - V7 - Imaj7`, tritone substitutions, extended chords like `Cmaj9`, `D9`, `F#m7b5`.
Rhythmic breakdown: `2/4`, `3/4`, `4/4`, syncopation, accent placement, clave patterns.
Harmonic/Melodic techniques: voice leading, modal interchange, altered scales, basslines.
Historical context: J.S. Bach, Beethoven, landmark recordings.
I will structure it exactly as requested.
I will ensure the German is professional and accurate.
I will add the GitHub alerts.
I will add ASCII rhythm grids.
I will add the practice challenge and glossary.
All constraints met. Generating.
Output matches the response.
```
