procedural-lofi

# Procedural Lofi — build a soundtrack in code, not in a sample pack This skill is the end-to-end recipe for a lofi bed (and its sibling ambient sounds: rain, keystrokes, door chimes, printer, water cooler…) that is **synthesized at runtime from constants** — zero audio files, zero royalties, and no two minutes ever sound the same. It was proven out on a real shipping product (an animated pixel-art office that plays ambient sound scaled by how busy the on-screen agents are), then distilled here. Two documents ship alongside this one: - **`reference/LOFI-BIBLE.md`** — the parameter tables. Harmony (chord grammar, voice-leading, register clamps), groove (swing %, drag ms, velocity curves), per-voice sound design (pad / bass / EP keys / sparkle / drums / texture / tape chain), mix targets (band shares, HPF strategy, loudness), and generative lessons from prior art. Every number is cited and, where it conflicts with a measurement, the measurement wins. - **`scripts/`** — the Python (numpy) pipeline: `analyze_*.py` (fingerprint a reference), `synth_audition.py` (a runnable numpy synth that produces `.wav` auditions), and `export_score.py` (freeze a good take into a constants table for the port). Read those two when you reach the step that needs them. This file is the map. --- ## The core idea (why code, not samples) A sampled lofi loop is: (a) a licensing liability, (b) heavy to bundle, and (c) audibly repetitive — the human brain catches a loop seam on the 3rd ...