vbth/choir-practice

> “Sunday morning, he’s rehearsing for his choir … and I’m the one who has to face the music.” — A tenor’s duck
English | Deutsch
## Your voice. Your custom sheet music. Practice anywhere.
Documentation of an agentic AI music workflow and skill developed for and with Claude Code as a private code experiment. It is only a “proof of concept”.
A choir score goes in, and an “AI-checked” ZIP comes out with 10 practice recordings for every voice.
Website with example pack and player: https://choir-practice-skill.pages.dev/en/
Example pack (ZIP, about 55 MB, from the release): All My Ducklings
Contents
1. Overview – What does it do?
2. Result – What comes out?
3. Workflow – Which steps are there?
4. Audio mix – How are the recordings mixed?
5. AI marking – How is AI content marked?
6. Limits – What can’t it do?
7. Requirements – What is needed?
8. Rights – What does the skill ask?
9. Licence – What is allowed?
10. Development – How to continue?
11. Flexibility – Is the workflow binding?
## 1. Overview – What does it do?
In: the score as PDF, photo, scan or export from notation software.
Out: one ZIP with
practice audio (MP3) and MIDI per voice: solo, with accompaniment, in the choir, plus tutti; in choir and piano sound; normal and slowed down
tags in every MP3 (title with piece, number and content, album per voice and sound, track number, composer, AI note) and an album cover: one per piece, the same for all voices, colours derived from key, mode, tempo and metre, title legibility checked
one ready-made ZIP per voice, a guide for the choir director, a check log and a correction log
a start page (Start.html) in the delivery folder and in every voice folder: structure with links, the chosen layouts with previews of the piece, and a mixer for the voices and the piano; in the voice folders also a player with headphones. It works with a double click, no server needed
## 2. Result – What comes out?
MP3 titles, file names, PDFs and logs follow the language of the conversation (German and English built in, see README.de.md). One ZIP, named like the top folder:
text
ChoirPractice /
├─ Start.html (structure with links, layouts with previews of the piece, mixer; open it with a double click)
├─ 1Scores/
│ ├─ 1Score Scan.pdf
│ ├─ 2Score .pdf
│ ├─ 3MusicXML Choir.musicxml
│ ├─ 4MusicXML Piano.musicxml
│ ├─ 5Layouts / (only the layouts you chose, grouped by voice: /04 Layout…/ Score L04.pdf)
│ └─ 6MIDI /
│ ├─ SMIDI / (one per voice: S, A, T, B; ten files)
│ └─ TuttiMIDI / (choir and piano)
├─ 2Practice/
│ ├─ 1Overview.pdf
│ ├─ 2Guide.pdf
│ └─ SPractice .zip (one ZIP per voice, ready to pass on)
│ ├─ 1SGuide.pdf
│ ├─ 2SLayouts / (the chosen layouts of this voice, one folder per layout; later numbers move up if none)
│ ├─ 3SScore .pdf
│ ├─ 4SAudioChoirSound / (six MP3: solo, with piano, each slow and normal; own voice louder; all voices equal)
│ ├─ 5SAudioPianoSound / (the same six)
│ ├─ 6STechnicalMixer / (startmixer.js: only the tracks of the mixer, do not open)
│ └─ Start.html (this voice: structure, layouts, player with headphones, mixer)
├─ 3Documentation/
│ ├─ 1README
│ ├─ 2CheckLog
│ ├─ 3CorrectionLog
│ └─ 4SessionHandoff .md
└─ 4Tools/