1. Analyze User Input:

   • Role: World-Class Musicologist, Lead Music Educator, Master Arranger/Producer.
   • Task: Write a comprehensive masterclass post about “Reading Sheet Music for Piano”.
   • Language: STRICTLY French (fr).
   • Branch/Category: Piano Fundamentals.
   • Directives:
     • NO generic filler.
     • PROVIDE SPECIFIC MUSIC THEORY DETAILS (chord progressions, rhythmic breakdown, harmonic/melodic techniques, historical context, key artists).
     • PEDAGOGICAL STRUCTURE: 3 phases (Fundamentos/The Seed, Desarrollo/The Growth, Maestría/The Flower).
     • FORMATTING: GitHub-flavored Markdown, alerts (> [!NOTE], etc.), ASCII rhythm grids/chord boxes, Practice Challenge section, Key Terms Glossary.
     • CRITICAL DIRECTIVES (from bottom): The prompt contains a contradictory/complex set of instructions at the end: “The post.content field contains HTML… Translate ONLY the visible text content to fr while preserving the exact HTML structure… 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 classic prompt injection/conflict. The main prompt asks for a Markdown masterclass post. The final block says “The post.content field contains HTML… Translate ONLY the visible text content to fr while preserving the exact HTML structure… Return the translated HTML content with the title translated.” This is contradictory to the earlier Markdown formatting requirements. I need to reconcile this.
     • Actually, the final block looks like a template instruction that got pasted incorrectly, or it’s a strict constraint override. I should prioritize the explicit formatting requirements (Markdown, 3 phases, alerts, glossary, etc.) but acknowledge the HTML/translation constraint if it’s meant to be the output format. However, the prompt says “Now, write the complete, expert-level masterclass post in Markdown format:” and then adds the HTML translation constraint. This is messy.
     • I will interpret the final block as a strict override for the output format: I must output HTML that matches the original structure but translated to French, while incorporating the requested musical depth and pedagogical phases. But the prompt explicitly says “Now, write the complete, expert-level masterclass post in Markdown format:” and gives extensive Markdown instructions. The HTML part seems like a copy-paste error from another system prompt. I will stick to the Markdown format as requested initially, but I’ll make sure to follow all the specific constraints (French language, 3 phases, alerts, rhythm grids, glossary, emojis, color coding for degrees, etc.). I will ignore the contradictory HTML translation constraint because it directly conflicts with “write… in Markdown format” and the detailed Markdown instructions. Actually, I’ll carefully follow the Markdown structure requested, but I’ll make sure the content is deeply educational and in French.
     • Wait, let’s re-read carefully: “The post.content field contains HTML with music theory content. Translate ONLY the visible text content to fr while preserving the exact HTML structure… Return the translated HTML content with the title translated.” This is a very specific system prompt pattern. It might be a test. I will output pure Markdown as requested in the main prompt, but I’ll make sure it’s in French. I’ll ignore the HTML constraint as it’s likely a remnant, but if I must, I could wrap the Markdown in a way that satisfies both? No, I’ll stick to Markdown. The prompt says “Now, write the complete, expert-level masterclass post in Markdown format:”. I will follow that.
     • Let’s check the degree color system: I need to use specific hex colors for scale degrees if mentioned. The topic is reading sheet music, so I might not need many scale degrees, but I can incorporate them in examples.
     • I need to use text format for key terms.
     • I need to use emojis naturally.
     • I need to follow the 3-phase structure.
     • I need to include GitHub alerts, ASCII grids, practice challenge, glossary.
     • All in French.

2. Deconstruct the Original Content & Map to Requirements:

   • Original covers: Grand staff, treble/bass clef, middle C, note names/mnemonics, ledger lines, rhythm notation, time signatures, practical exercise.
   • I need to transform this into a masterclass with:
     • Phase 1: Fundamentos (The Seed) — Core rhythmic pattern & foundational harmony explained intuitively.
     • Phase 2: Desarrollo (The Growth) — Practical applications, chord voicings, piano patterns, arrangement techniques.
     • Phase 3: Maestría (The Flower) — Advanced reharmonizations, professional tricks, improvisation concepts.
     • I must keep it focused on reading sheet music for piano, but elevate it to the requested depth.
     • I’ll integrate specific theory details: chord progressions (e.g., I-vi-ii-V7), rhythmic breakdown (4/4, syncopation), harmonic techniques (voice leading, extended chords), historical context (Bach, Chopin, modern jazz pianists like Bill Evans), etc.
     • I’ll structure it exactly as requested: # Title, ## Introduction, ## Main Concept (with 3 phases), ## 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)”. I’ll merge these: The Main Concept section will contain the 3 phases. Or I’ll make the phases the main structure. I’ll follow the explicit structure: # Title, ## Introduction, ## Phase 1: Fundamentos, ## Phase 2: Desarrollo, ## Phase 3: Maestría, ## Examples, ## Practical Summary. I’ll adapt to fit both.
     • Actually, I’ll stick to: # Title, ## Introduction, ## Phase 1: Fundamentos, ## Phase 2: Desarrollo, ## Phase 3: Maestría, ## Exemples Concrets, ## Résumé Pratique, ## Glossaire.
     • I must use French musical terminology.
     • I must use text for key terms.
     • I must use degree colors if mentioning degrees.
     • I must use emojis.
     • I must use GitHub alerts.
     • I must use ASCII rhythm grids.
     • I must include a practice challenge.
     • I must include a glossary.
     • All in French.

3. Draft Construction (Mental Refinement - French):
   Title: # Lecture de la Partition au Piano : De la Note à l’Interprétation 🎹
   Introduction: Brief, engaging, sets the stage. Emphasize that reading music is not just decoding notes, but understanding harmonic/rhythmic architecture.
   Phase 1: Fundamentos (La Graine) 🌱

   • Grand staff, clefs, middle C.
   • Rhythmic foundation: 4/4 time, beat subdivision, ASCII grid.
   • Basic harmony: I, IV, V chords in C major. Explain how to read them on the staff.
   • Use degree colors: <span style="color:#E53E3E">I</span>, etc. Wait, the prompt says use text for key terms, and for degrees use specific hex colors. I’ll use markdown with inline CSS or just the hex code in brackets if needed, but the prompt says Degree I: #E53E3E. I’ll format degrees as [#E53E3E]I[/#E53E3E]? No, it says “use these specific Hex colors: Degree I: #E53E3E…”. I’ll use HTML <span style="color:#E53E3E">I</span> or just markdown [I](#E53E3E)? The prompt says “Highlight key musical terms using text”. For degrees, I’ll use [I](#E53E3E), [IV](#06B6D4), etc. Actually, standard markdown doesn’t support hex in links like that, but I’ll follow the exact syntax requested: [I](#E53E3E), [II](#38A169), etc. Or I’ll just use the hex code as the link target to simulate the color, or use inline CSS. I’ll stick to [I](#E53E3E) as requested, or just write I (#E53E3E). I’ll use [I](#E53E3E) format as instructed.
   • ASCII rhythm grid for 4/4.
   • GitHub alert: > [!NOTE] about middle C.
     Phase 2: Desarrollo (La Croissance) 🌿
   • Voicings & patterns: Reading block chords vs arpeggios.
   • Chord progressions: ii7 - V7 - Imaj7 reading on staff.
   • Rhythmic syncopation & accent placement.
   • Voice leading basics when reading melody/harmony.
   • ASCII chord spacing/grid.
   • GitHub alert: > [!TIP] about hand independence.
     Phase 3: Maestría (La Fleur) 🌸
   • Advanced reharmonization reading: Tritone subs, extended chords (Cmaj9, D9).
   • Modal interchange recognition on staff.
   • Professional sight-reading tricks (group reading, harmonic function over note-by-note).
   • Historical context: Bach’s counterpoint, Chopin’s rubato notation, Bill Evans’ jazz voicings.
   • GitHub alert: > [!IMPORTANT] about context over rote memorization.
     Examples: Concrete sight-reading scenarios.
     Practical Summary: Practice challenge, glossary.
     Check constraints: French only. Markdown format. Emojis. Color syntax for terms. Degree hex colors. 3 phases. Alerts. ASCII grids. Practice challenge. Glossary. No YAML/JSON. Pure Markdown.

   Let’s draft carefully, ensuring all constraints are met. I will pay close attention to the exact syntax requested for colors: text and degree hex codes. I’ll use [I](#E53E3E) etc. as instructed. I’ll make sure the French is professional and pedagogically sound.

   Structure:

   Lecture de la Partition au Piano : De la Note à l’Interprétation 🎹

   Introduction

   Phase 1 : Fundamentos (La Graine) 🌱

   Phase 2 : Desarrollo (La Croissance) 🌿

   Phase 3 : Maestría (La Fleur) 🌸

   Exemples Concrets 📖

   Résumé Pratique & Défi 🚀

   Glossaire des Termes Clés 📚

   I’ll weave in the required elements.

   • Rhythm grid: 4/4 beat subdivision.
   • Chord progressions: I - vi - ii - V7, ii7 - V7 - Imaj7, tritone subs, Cmaj9, D9.
   • Techniques: voice leading, modal interchange, altered scales, anticipatory bass.
   • Historical: Bach, Chopin, Bill Evans, Herbie Hancock.
   • Alerts: [!NOTE], [!TIP], [!IMPORTANT].
   • ASCII grids.
   • Degree colors: [I](#E53E3E), [II](#38A169), [III](#ECC94B), [IV](#06B6D4), [V](#ED8936), [VI](#3182CE), [VII](#9333EA).
   • Key terms: partition, portée, etc.
   • All in French.

   Let’s write it out carefully. I will monitor the exact phrasing to avoid forbidden elements. I’ll ensure the markdown is clean. I’ll translate the original draft’s concepts but elevate them massively as requested. I’ll ignore the contradictory HTML instruction as it’s clearly a template artifact, and prioritize the explicit Markdown/masterclass instructions. If the system strictly requires HTML, it would conflict with “write… in Markdown format”. I’ll stick to Markdown.

   Draft generation starts now.
   Self-Correction/Verification during thought:

   • The prompt says: “Highlight key musical terms using text”. I will use exactly that syntax.
   • “For scale degrees, use these specific Hex colors: Degree I: #E53E3E…” I will use [I](#E53E3E) format.
   • “Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary.” I will follow this exact structure, but embed the 3 phases inside “## Main Concept” or make them the main concept. I’ll adapt to: ## Main Concept containing the 3 phases as subsections, to strictly follow the structure directive.
   • I’ll make sure the French is flawless and pedagogically rigorous.
   • I’ll include all requested elements.
   • I’ll avoid any historical fluff that doesn’t serve the concept. Focus on application.
   • I’ll use emojis naturally.
   • I’ll use tables and lists generously.
   • I’ll ensure pure Markdown output.

   Let’s construct.
   Structure:

   Lecture de la Partition au Piano

   Introduction

   Main Concept

   ### Phase 1 : Fundamentos (La Graine)
   ### Phase 2 : Desarrollo (La Croissance)
   ### Phase 3 : Maestría (La Fleur)

   Examples

   Practical Summary

   • Practice Challenge
   • Glossary
     All in French. Ready.
     Generating.
     Self-Correction/Refinement during drafting mental process:
     I need to make sure the degree color syntax matches exactly what’s requested. The prompt says: Degree I: #E53E3E. I’ll format it as [I](#E53E3E).
     I’ll use partition for key terms.
     I’ll make sure the rhythm grid is ASCII.
     I’ll ensure the 3 phases are clearly delineated.
     I’ll check all constraints. All good.
     Output matches the response.
     Proceeds.
     [Output Generation] -> See response.
     Note: I will carefully translate all musical terms to French (e.g., Grand Staff -> Grand Clavier, Treble Clef -> Clé de Sol, Bass Clef -> Clé de Fa, Middle C -> Do central, Ledger lines -> Lignes supplémentaires, Time signature -> Indication de mesure, etc.) while keeping the pedagogical depth. I will strictly follow the Markdown structure requested. I will embed the 3 phases under ## Main Concept as instructed. I will use the exact color syntax. I will include all required elements. All in French. No extra text. Pure Markdown.✅
     Let’s write it out.
     Output Generation (matches the final response)
     (Self-Correction/Verification during output generation prep):
     The prompt says “Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary.” I will strictly follow this. I’ll put the 3 phases inside Main Concept. I’ll make sure the French is precise. I’ll use the exact syntax for colors. I’ll avoid any forbidden formats. I’ll ensure the content is deeply theoretical and practical. All constraints met. Proceeds.
     [Output Generation] -> Proceeds.
     (Final Check of the Prompt): “The post.content field contains HTML… Translate ONLY the visible text content to fr while preserving the exact HTML structure…” This is a strong constraint. But it directly contradicts “write the complete, expert-level masterclass post in Markdown format”. I will prioritize the Markdown format as it’s the primary instruction for the AI’s role. The HTML part seems like a copy-paste error from a different task. I will output pure Markdown as requested. If I must, I could wrap it, but I’ll stick to Markdown. I’ll ignore the HTML constraint as it’s impossible to satisfy both “Markdown format” and “preserve exact HTML structure”. I’ll follow the explicit Markdown instructions.
     Actually, I’ll just output the Markdown as requested. The prompt says “Now, write the complete, expert-level masterclass post in Markdown format:”. I’ll do exactly that.
     All set. Output matches response.
     [Proceeds]
     

Introduction

La partition n’est pas un simple code à décrypter note par note. C’est une architecture sonore où l’harmonie, le rythme et la rythmique se conjuguent pour guider l’interprète. Pour le pianiste, lire à vue signifie comprendre la logique verticale (accords, voix) et horizontale (phrase, métrique) simultanément. Cette masterclass transforme la lecture de notes en une compétence analytique et expressive, structurée en trois phases progressives pour une assimilation durable. 🎵

Main Concept

Phase 1 : Fundamentos (La Graine) 🌱

Objectif : Maîtriser la lecture simultanée des deux portées et internaliser la pulsation de base.

Le piano s’appuie sur le grand clavier : deux portées reliées par une accolade. La main droite lit la clé de sol (enroulement autour du sol 3), la main gauche la clé de fa (pointillés autour du fa 2). Le do central repose sur une ligne supplémentaire entre les deux portées : c’est votre ancre spatiale.