TypeScript source
Readable engine code designed to live in your repo, with a small API surface and no runtime dependency chain.
A source-included audio engine for games and interactive web apps: small TypeScript/WebAudio code, manifest-driven sounds, music crossfades, buses, fades, and documentation you can actually ship with.
AI can draft an audio wrapper. That is not the hard claim. The real cost is cleaning the result: dependency drift, license risk, half-finished state handling, undocumented assumptions, and code that becomes hard to trust after the prototype works.
CleanAudio is positioned differently: a small, checked, documented audio layer that AI builders can drop into a web game or interactive app without inheriting runtime dependencies, GPL/AGPL obligations, questionable assets, or architectural junk.
It is source-included commercial kit code, not a mystery package and not a bloated framework.
CleanAudio keeps the public API direct enough for AI-generated game code to use reliably, while hiding the repetitive browser audio details behind one consistent engine.
const audio = await createAudioEngine({ masterVolume: 0.8 });
await audio.loadManifest("/audio/manifest.json");
await audio.play("ui.click");
await audio.music.crossfade("battle", { seconds: 2 });
await audio.bus("music").fadeTo(0.4, { seconds: 1 });
The first Clean Kit is focused on the audio layer that most AI-built games need early and then keep rewriting under pressure.
Readable engine code designed to live in your repo, with a small API surface and no runtime dependency chain.
Load named sounds from a JSON manifest, then trigger UI sounds, game events, ambience, and music by stable ids.
Master volume, music groups, fade controls, and crossfades for menus, battles, cutscenes, and app transitions.
Integration notes and examples written for fast AI-assisted builds, not just for library authors.
No GPL/AGPL tail and no bundled unclear assets. You bring your own audio files and keep the chain understandable.
No framework takeover, no audio editor UI, no server requirement. It is the layer under your actual product.
This kit is for builders who already use AI heavily but still need a clean, reviewable subsystem when the prototype starts turning into a product.
The product is ready enough to present as the first kit in the line, but the public checkout and final terms should stay gated until license delivery, support path, and sales operations are clean.
Price, final license text, download delivery, and support contact should be published before checkout opens. The preview API can still refine before v1.