πŸ“˜ Resource Creation Guide

Use AI prompts and the importer to build shareable lists.

Learn how to create high-quality resource lists using AI tools and our import system.

πŸ€– Using ChatGPT for Resource Curation

✨ Take the Fear Out of Using ChatGPT

Never used ChatGPT before? No worriesβ€”it's easier than you think!

Here's the secret: you can just talk to it like you're talking to a colleague. Head over to ChatGPT.com (you'll need a free account), and start a conversation about what you're looking for.

For example, you could type:

  • "I need resources for teaching Baroque keyboard repertoire to intermediate piano students"
  • "Find me websites with free sheet music for elementary choir"
  • "What are the best online tools for teaching music theory?"
  • "I want articles about building a private music studio"

ChatGPT will respond with ideas, suggestions, and links. It's like having a research assistant who never sleeps!

🎯 The Secret Sauce: Structured JSON

Now here's where it gets powerful for Professional Music Teachers of New Mexico members: instead of just getting a conversational response, we've created special prompts that make ChatGPT output perfectly formatted data that you can paste directly into our importer.

These prompts are like giving ChatGPT a template to fill out. You'll get back organized lists with titles, descriptions, and URLsβ€”ready to share with the entire PMTNM community in seconds. No copying and pasting individual links, no formatting headaches.

πŸ’‘ Bottom Line: You can use ChatGPT however you wantβ€”casual conversation or our structured prompts below. But if you want to contribute resources to PMTNM instantly, our prompts are the fastest way from idea to published list.

1PMTNM JSON Prompt (Copy & Paste)

This is our "secret sauce" prompt that formats everything perfectly for our importer. Copy it, paste it into ChatGPT, add your specific topic at the end, and hit enter!

You are curating teacher-focused music resource lists for Professional Music Teachers of New Mexico. Create JSON data for resource lists. Audience is music teachers; include classroom-ready items and articles. Use reputable, stable sources. Prefer free/open content; if paywalled, choose high value. 🚨 CRITICAL JSON FORMATTING RULES (CHATGPT MUST FOLLOW): 1. Output ONLY valid JSON - no markdown, no code blocks, no explanations 2. URLs must be PLAIN TEXT strings - NEVER use markdown link syntax [text](url) 3. DO NOT wrap JSON in ```json or ``` code blocks 4. DO NOT use markdown formatting anywhere in the output 5. Email addresses must be plain text - NEVER use mailto: links 6. Match this schema EXACTLY - no extra fields, no comments VALID JSON SCHEMA (copy this structure exactly): { "lists": [ { "title": "Descriptive List Title", "description": "One-sentence overview for teachers.", "category": "music_theory", "is_public": true, "urls": [ { "title": "Resource Name (NOT the URL)", "url": "https://example.com/full/path", "description": "Why teachers need this. 1-2 sentences." } ] } ] } VALID CATEGORIES (use exactly one of these): - music_theory - sheet_music - teaching_resources - professional_development - organizations - technology_tools - student_resources EXAMPLE OF CORRECT URL FORMAT: βœ… CORRECT: "url": "https://www.musictheory.net/lessons" ❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)" ❌ WRONG: "url": "[https://www.musictheory.net](https://www.musictheory.net)" YOUR TASK: Create 3-4 lists (different categories). Each list should have 5-8 URLs. Focus on:

2Customization Tips

  • Specify instruments: Add "for piano/voice/guitar teachers" to target specific instruments
  • Target grade levels: Add "for elementary/middle/high school students" for age-appropriate resources
  • Add curriculum focus: Include "aligned with [state standards/curriculum]" if needed
  • Request specific formats: Ask for "video tutorials," "printable worksheets," or "interactive tools"
  • Specify topics: Add "focusing on [Baroque repertoire/jazz theory/sight-reading]" etc.
πŸ’‘ Pro Tip: If ChatGPT outputs markdown links like [text](url), our importer will automatically clean them! But the new prompts should prevent this.

πŸ“₯ Using the Resource Importer

1Save Your JSON

After ChatGPT generates your JSON:

  1. Copy the entire JSON output (including the outer curly braces)
  2. Save it as a .json file (e.g., my_resources.json)
  3. Verify it's valid JSON using an online validator if unsure

2Import Your JSON

Easy Web Import: Use our web-based importer (recommended):

Simply copy your ChatGPT JSON and paste it into the web form. The system will validate and import your lists automatically.

For Administrators: Use the CLI importer:

cd /path/to/pmtnm/project php scripts/seed_shared_lists.php path/to/your/file.json

3Verification

After import, check:

  • Visit the Shared Resources page
  • Confirm your lists appear in the correct categories
  • Test a few URLs to ensure they're accessible
  • Verify descriptions are helpful and accurate

🎼 Instrument-Specific Prompts

Use these specialized prompts for targeted resource lists:

🎹 Piano

Click to view prompt
Create piano-focused resource lists for music teachers. Include method books, technique resources, repertoire databases, and performance practice guides. Target both classical and contemporary styles. Categories: teaching_resources, music_theory, professional_dev, organizations.

Focus on:
- Progressive method books and supplementary materials
- Technical studies and etude collections
- Sheet music libraries (IMSLP, Henle, etc.)
- Pedaling, fingering, and interpretation guides
- Piano pedagogy conferences and organizations

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

🎻 Violin

Click to view prompt
Create violin pedagogy resource lists for string teachers. Include method books, bowing techniques, intonation tools, and orchestral repertoire. Cover both solo and ensemble teaching.

Focus on:
- Suzuki, Essential Elements, and traditional methods
- Bowing technique videos and exercises
- Intonation apps and tuning resources
- Orchestral excerpt libraries
- String pedagogy workshops and masterclasses

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

🎀 Voice

Click to view prompt
Create vocal pedagogy resource lists for voice teachers. Include vocal health, diction resources, repertoire by voice type, and performance anxiety management.

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

🎸 Guitar

Click to view prompt
Create guitar pedagogy resource lists covering classical, acoustic, and electric guitar teaching. Include technique development, repertoire, and technology tools.

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

🎺 Band Instruments

Click to view prompt
Create band instrument resource lists for woodwind, brass, and percussion teachers. Include embouchure development, ensemble skills, and marching band resources.

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

🎡 General Music

Click to view prompt
Create general music education resource lists for elementary and secondary classroom teachers. Include curriculum guides, multicultural resources, and technology integration.

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

🎼 Composer & Genre-Specific Prompts (Nerd Mode)

Deep-dive prompts for focused curation around composers, techniques, and styles.

🎹 J. S. Bach β€” WTC & Contrapuntal Craft

Click to view prompt
Curate resources for teaching and analyzing Bach's counterpoint (focus: WTC I/II, Inventions/Sinfonias). Include: voice-leading strategies, species-to-free counterpoint bridges, invertible counterpoint, stretto/augmentation/diminution, subject design, modulatory plans, and figured-bass realisation pedagogy. Favor primary sources, scholarly editions, and reputable analysis blogs/videos.

Focus on teacher utility: annotated scores, assignment-ready drill pages, interactive fugue visualizers, and choir/instrumental transcriptions.

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

🌊 Debussy β€” Impressionist Harmony & Timbre

Click to view prompt
Curate resources on Debussy's harmonic language (planing, modal mixture, pentatonic/whole-tone/octatonic collections), orchestration color, and rubato/agogic practice. Include lesson-ready analyses (e.g., Voiles, Pagodes, La cathΓ©drale engloutie), annotated scores, ear-training tasks for coloristic sonorities, and performance/recording comparisons.

Include reputable theory texts, university lectures, and score-linked audio. Provide classroom tasks translating analysis into piano/ensemble activities.

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

πŸͺ— BartΓ³k β€” Axis System, Polymodal Chromaticism

Click to view prompt
Curate resources explaining BartΓ³k's axis system, polymodal chromaticism, symmetrical structures, and folk-source integration. Include class-ready analyses (Mikrokosmos selections, String Quartets excerpts, Romanian Folk Dances), set-class summaries (Forte numbers), and rhythmic cells.

Provide drills mapping scales/axes, listening lists, and assignments connecting analysis to performance choices (bowings/articulation/pedaling).

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

πŸ” Minimalism β€” Process & Phase

Click to view prompt
Curate resources on process music (Reich, Glass, Riley): phasing, additive/subtractive processes, resultant patterns, and ensemble coordination strategies. Include annotated scores, rehearsal methods, click/track tools, and student projects (DAW-based process building).

Favor reputable analyses, composer interviews, and classroom-tested activities.

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

πŸ§ͺ Serialism β€” Rows, Invariants, and PC-Set Tools

Click to view prompt
Curate resources teaching 12-tone basics (row construction, transformations, invariants), and practical set-theory tools (interval-class vectors, complements, Z-related sets). Include row-work worksheets, web row matrix generators, and examples (Webern Op. 5/27/28; Schoenberg Op. 25; Babbitt).

Provide teacher-ready tasks connecting analysis to rehearsal strategies (intonation of unordered collections, articulation mapping).

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

🎷 Jazz Harmony β€” Functional, Modal, Reharm

Click to view prompt
Curate resources on jazz harmony for teachers: functional changes (bebop ii–V–I variants), modal harmony, tritone subs, backdoor ii–V, Coltrane changes, and modern reharmonization. Include transcribable examples, play-along tools, voicing maps (drop-2/4th stacks), and classroom assignments.

Favor authoritative texts, university materials, and curated playlists with score links.

🚨 CRITICAL: Output ONLY valid JSON. NO markdown, NO code blocks, NO ```json wrapper, NO explanations.

EXACT JSON SCHEMA TO FOLLOW:
{
  "lists": [
    {
      "title": "TITLE",
      "description": "One-sentence overview for teachers.",
      "category": "music_theory",
      "is_public": true,
      "urls": [
        { 
          "title": "Resource Title", 
          "url": "https://full-url-here.com/path", 
          "description": "Why this is useful for teachers/classroom. 1–2 sentences." 
        }
      ]
    }
  ]
}

FORMATTING RULES (CRITICAL - MUST FOLLOW):
1. URLs must be PLAIN TEXT - NEVER use [text](url) markdown syntax
2. NO markdown links anywhere in the output
3. NO mailto: links - just plain email addresses if needed
4. NO code blocks (```json or ```) wrapping the JSON
5. Output STARTS with { and ENDS with } - nothing else

VALID CATEGORIES (use exactly these strings):
- music_theory
- sheet_music
- teaching_resources
- professional_development
- organizations
- technology_tools
- student_resources

CONTENT REQUIREMENTS:
- Provide 3-4 lists (different categories)
- Each list should have 5-8 URLs (total ~20 items across all lists)
- Titles: clear, human-friendly (not just domain names)
- Descriptions: concise, teacher-focused, actionable
- URLs: verified, canonical, educational
- Mix formats: articles, tools, PDFs, videos
- No duplicates

EXAMPLE URL FORMATS:
βœ… CORRECT: "url": "https://www.musictheory.net/lessons"
βœ… CORRECT: "url": "https://imslp.org/wiki/Main_Page"
❌ WRONG: "url": "[musictheory.net](https://www.musictheory.net/lessons)"
❌ WRONG: "url": "[https://imslp.org](https://imslp.org/wiki/Main_Page)"

QUALITY BAR:
- Authority/widely-used educator tools (musictheory.net, IMSLP, Oxford, JSTOR, MTNA/NAfME, universities)
- Practical classroom applicability or professional development value
- If paywalled, landing page must justify inclusion

OUTPUT: Return ONLY the JSON object. Start with { and end with }. No markdown formatting.

βœ… Quality Guidelines

Source Credibility

  • Prefer: Educational institutions, professional organizations (MTNA, NAfME), established publishers
  • Include: Peer-reviewed journals, conference proceedings, recognized pedagogues
  • Avoid: Personal blogs without credentials, commercial-only sites, outdated resources

Accessibility & Usability

  • Test all URLs before submitting
  • Prefer mobile-friendly and accessible websites
  • Include mix of free and premium resources
  • Write clear, actionable descriptions

Content Balance

  • Variety: Mix articles, videos, interactive tools, and downloadables
  • Levels: Include resources for different skill/grade levels
  • Perspectives: Represent diverse teaching approaches and cultural viewpoints
  • Timeliness: Favor recent resources while including timeless classics

πŸ”§ Troubleshooting

Common JSON Errors

  • Missing commas: Ensure commas between array items and object properties
  • Trailing commas: Remove commas after the last item in arrays/objects
  • Quote marks: Use double quotes, not single quotes
  • Escaping: Escape quotes in descriptions with \"

Import Issues

  • Invalid email: Ensure creator_email matches a registered user
  • Category mismatch: Use only: music_theory, teaching_resources, professional_development, organizations
  • URL validation: Check that all URLs are properly formatted with http:// or https://

Getting Help

If you encounter issues:

  • Contact beta-helper@pmtnm.org with your JSON file
  • Include any error messages you received
  • Describe what you were trying to accomplish