Skip to main content
Auto-memory
Retell + Twilio
MCP ecosystem
Founder Pres.
Obsidian + QMD
Review pass
Claude / Codex
Convex
75K+ sold
SwiftUI CloudKit
Next.js + Vercel
1,350+ locations
Shopify
Session notes
Founder
MCP forks
<60s response
Operator chapters
QMD retrieval
121+ skills
Six figures raised
Founder office
back to grid
Projects2026

Wedding DJ Mixer

I'm not a DJ. I needed a mix-ready wedding set, so I built a Python program with AI in the research and audit loop. It turns one Spotify playlist into an ordered DJ.Studio handoff.

Not a DJ
needed a real set order
One playlist
turned into a DJ.Studio handoff
Python CLI
runs fetch to export
AI loop
research and audit passes
§01The workLive system

What the program does: turn a Spotify playlist into a rule-checked DJ.Studio handoff.

The work

Playlist in. Mix-ready plan out.

Research and audit passes shape the set order, then it exports files I can review and play in DJ.Studio.

AI-assisted order planSet builderSpotify to DJ.Studio
01 · InputFetch the playlist.
02 · RulesBuild the sequencing rules.
03 · OrderSequence and audit.
04 · HandoffExport for DJ.Studio.
76
tracks
12
sequencing rules
5
export formats
v3.5
audited order
The workResearch and audit passes shape the set order, then it exports files I can review and play in DJ.Studio.
§02The pipelineEnd-to-end flow
01 · Input

Fetch the playlist.

The CLI pulls the public Spotify playlist, falls back to the embed page when the API path fails, and normalizes the 76 tracks.

Spotify · embed fallback
02 · Rules

Build the sequencing rules.

Research agents turn wedding-DJ writing into twelve rules: energy, singalongs, slow songs, genre runs, the close.

4 research passes
03 · Order

Sequence and audit.

The sequencer places every song, then an independent audit pass flags weak stretches and exact swaps before the final order ships.

v3.5
04 · Handoff

Export for DJ.Studio.

The output bundle gives DJ.Studio import files plus human-readable notes, so the final review happens in the tool that plays the set.

M3U8 · CSV · JSON · XLSX
§03What I builtCLI modules

A small Python CLI with separate modules for fetching, matching, sequencing, auditing, transitions, and exports.

Fetch the playlist, order the set, export the handoff.

The fetch module tries Spotify's Client Credentials API first, but that path 401'd on the real playlist, so it falls back to scraping the public embed page. Four research passes then t...

A private handoff bundle for one wedding set.

The final order was v3.5: 76 tracks placed, no same-artist adjacencies, slow songs separated, singalongs spaced, ready to import into DJ.Studio.

The private outputs.

Repo stays private, so the outputs are the proof.

§04Sequencing rules6 of 12 shown

It's mostly an ordering tool. These rules turned a playlist into a set order I could review and play.

Selected rules6 of 12
  1. Start with familiar songs while older guests are still dancing.
  2. Limit any one genre run to four or five songs.
  3. Separate slow songs with an immediate rebuilder.
  4. Space the biggest singalongs at least 28 minutes apart.
  5. Rotate age groups instead of holding one lane too long.
  6. Save the closer for the final slot.
§05ArtifactsPrivate outputs

Repo's private, so the artifacts are the output types: order, workbook, notes, import files.

wedding-mix CLI

Private Python CLI that turns a Spotify playlist into a DJ.Studio-ready handoff bundle.

private repo · scoped to one wedding
v3.5 audited order

76 tracks placed with same-artist checks, slow-song spacing, singalong spacing, and a final closer.

RECOMMENDED_ORDER.md
DJ.Studio handoff bundle

M3U8, CSV, JSON, five-sheet XLSX, transition notes, and a handoff letter for final review.

data/output
Research and audit notes

Four research passes, one synthesis, and one independent audit pass produced the sequencing rules and final swaps.

private