The Codebase Composer — A Repository as 90 Seconds of Music
Turn this codebase into a 90-second piece of music. Each module a motif. Each dependency a harmonic relationship. Cyclomatic complexity sets the tempo. Bug-fix frequency becomes percussion.
Why this exists
Architecture diagrams hide texture. Boxes and arrows make every system look equally tidy. Music refuses to lie. A frenetic codebase sounds frenetic. A bloated one sounds bloated. A codebase with one module doing all the work has a melody that won't stop screaming over the rest of the orchestra. The ear hears what the eye has been trained to glaze past.
What you get back
- A 90-second MIDI rendering of the codebase, playable anywhere.
- A written score annotating which file produced which note, which dependency produced which interval, which hot-spot produced which drum hit.
- A verdict on whether the piece is listenable.
- A diagnosis of what the unlistenable parts tell you about the structure underneath.
When to reach for this pattern
Onboarding presentations where a new engineer needs to feel the system before they read it. Conference talks that need a hook the slides can't deliver. Teaching architectural intuition to engineers who already know how to read a diagram and have stopped seeing one. Making technical health audible to non-technical leadership — a board hears thirty seconds of dissonance and understands the refactor budget without a single chart.
Analyze this codebase's structure and turn it into a 90-second piece
of music. Each module is a motif. Each dependency is a harmonic
relationship. Cyclomatic complexity sets the tempo. Bug-fix
frequency becomes percussion. Output a MIDI file and a written
score that names which feature of the codebase produced which
musical decision. The piece should be listenable, not noise.Paste this into Claude, Cursor, or Copilot. Change one thing that matters to you.
What I learned shipping it
- Architecture has texture. A diagram flattens it; a melody preserves it.
- Mapping code to a second sense surfaces what visual diagrams gloss over — rhythm, density, dissonance.
- If the piece is unlistenable, that's not a failure of the prompt. That's the codebase telling you something about itself.