Add sound effects to your game in one sentence, with an AI agent
We connected Claude Code to our free sound library and said “Add sound effects to my game.” It picked 16 matching sounds, wired them in and tested them. Play the result, then do it in your game.
This is the real result. Click it and play. Open full screen
What we asked“Add sound effects to my game.”
What happened
- Read the game and listed 16 moments that need a sound, from jumps to the chapter finish
- Asked the aigamedev.ai sound library for a matching set in one call
- Swapped the picks that didn't fit: a laser shot for the section flag, a sports buzzer for the chapter end, and jump and double jump the wrong way round
- Downloaded the 16 sounds into the project and played each one at the moment the game changes
- Added M to mute, and small pitch changes on jumps and landings
- Wrote a test that plays every event in a hidden browser and checks its sound fires
- Fixed the timing in its own test until all 23 tests passed
- Checked that every sound also loads when the game is opened straight from disk
Click the game and press a key to start the sound. Jump, double jump, hit a spring, touch the spikes, pick up the yellow orb and walk through the door. Each of those now has its own sound, and M mutes.
We started from the silent game from our platformer series and a fresh Claude Code session with nothing in it but our sound library’s server. One sentence, about six minutes, and no follow-up from us. You can hear the 16 sounds side by side on this page.
Do it in your game
- Connect your agent to the library once. It takes one line in Claude Code, or one setting in the Claude app, Cursor or VS Code. The steps for each are here.
- Open your game’s folder in the agent and say “Add sound effects to my game.” Any engine works. The library gives the agent short steps for Phaser, plain JavaScript, Godot, Unity and pygame.
- Play it, then fix what you don’t like in plain words. “The landing is too loud.” “Use a softer coin.” Every sound is a separate file, so a swap never touches the rest.
No agent? Pick sounds yourself in the sound library. All 949 are free to use in your games, commercial or not, with no credit needed.
What makes game sounds feel right
The agent followed these rules, and they are worth checking in any game, with or without AI:
- One style for the whole game. Sounds from different worlds sound wrong together even when each is good. Most of these come from one 8-bit pack, and the rest were picked to match it.
- Short sounds for quick actions. A jump or a pickup should be over in a fraction of a second. In an earlier run, the library’s first pick for the block shake was a 2.3-second rock slide. The block only shakes for half a second, so the agent chose a short crumble instead.
- Small changes on sounds you hear all the time. The same jump played 500 times starts to grate. Changing the pitch a little on every play keeps it fresh, a trick game audio designers use all the time (Game Developer). Our library also has sets of three or four versions of footsteps, hits and pickups for this.
- A sound only when something changes. The jump sound plays when the jump starts, not every frame while the player is in the air. Soft landings stay silent here, so only real falls make a thud.
- Browsers stay silent until the first click or key press. That is a browser rule, not a bug (Chrome’s autoplay policy). Games usually start their sound on the first input, like this one does.
- Always add a mute key. Players open games at work, on trains and late at night.
