From gamedev-threejs
Generate, convert, clean, and prepare audio assets for Three.js browser games using ElevenLabs. Use for sound effects, looping ambience, UI sounds, impact/weapon/vehicle audio, creature or boss stingers, announcer/dialogue TTS, scratch-performance voice conversion, voice cleanup/isolation, audio manifests, and game-ready web audio integration.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gamedev-threejs:threejs-audio-generatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create game-ready audio assets for Three.js projects. This skill consolidates game sound generation, voice generation/conversion, audio cleanup, credential probing, and runtime integration into one Three.js-focused production workflow.
Create game-ready audio assets for Three.js projects. This skill consolidates game sound generation, voice generation/conversion, audio cleanup, credential probing, and runtime integration into one Three.js-focused production workflow.
Provider: ElevenLabs.
Use this skill for:
For premium/AAA/showcase game work, audio is not cosmetic. Generate or integrate at least a minimal interaction audio set for the main loop unless the user explicitly requests mute/offline-only output or credentials/API attempts are blocked.
Never store API keys in skill files or browser/game code. The script checks:
--api-keyELEVENLABS_API_KEYBefore declaring the key unavailable, run the credential probe and paste its literal SET/MISSING output:
bash ~/.codex/skills/threejs-3d-generator/scripts/probe_asset_credentials.sh
For Claude installs:
bash ~/.claude/skills/threejs-3d-generator/scripts/probe_asset_credentials.sh
If the probe says ELEVENLABS_API_KEY=SET but the script sees no key, run through a shell that sources the user's profile:
zsh -c 'source "$HOME/.zprofile" 2>/dev/null; source "$HOME/.zshrc" 2>/dev/null; python3 ~/.codex/skills/threejs-audio-generator/scripts/threejs_audio_asset.py probe'
Load references/audio-workflows.md before building a game audio plan, generating multiple assets, wiring runtime audio, cleaning/converting voices, or claiming premium game audio.
Track it in the reference ledger. Do not mark the audio phase complete while this reference is skipped.
Run from the user's current game project directory:
python3 ~/.codex/skills/threejs-audio-generator/scripts/threejs_audio_asset.py --help
Claude install path:
python3 ~/.claude/skills/threejs-audio-generator/scripts/threejs_audio_asset.py --help
Probe:
python3 ~/.codex/skills/threejs-audio-generator/scripts/threejs_audio_asset.py probe
Generate SFX:
python3 ~/.codex/skills/threejs-audio-generator/scripts/threejs_audio_asset.py sfx \
--prompt "tight futuristic boost pickup, bright transient, short sparkling tail, arcade racing game" \
--duration 1.2 \
--prompt-influence 0.65 \
--out assets/audio/sfx/boost-pickup.mp3
Generate looping ambience:
python3 ~/.codex/skills/threejs-audio-generator/scripts/threejs_audio_asset.py sfx \
--prompt "seamless cyber resort mini golf ambience, distant surf, soft neon transformer hum, gentle crowd bed" \
--duration 12 \
--loop \
--prompt-influence 0.45 \
--out assets/audio/ambience/cyber-resort-loop.mp3
Generate TTS/announcer line:
python3 ~/.codex/skills/threejs-audio-generator/scripts/threejs_audio_asset.py tts \
--text "Perfect shot." \
--voice-id JBFqnCBsd6RMkjVDRZzb \
--out assets/audio/voice/perfect-shot.mp3
Clean dialogue:
python3 ~/.codex/skills/threejs-audio-generator/scripts/threejs_audio_asset.py isolate \
--input assets/audio/source/noisy-boss-line.wav \
--out assets/audio/voice/boss-line-clean.mp3
Convert a scratch performance to a target voice:
python3 ~/.codex/skills/threejs-audio-generator/scripts/threejs_audio_asset.py voice-change \
--input assets/audio/source/scratch-boss-line.wav \
--voice-id JBFqnCBsd6RMkjVDRZzb \
--remove-background-noise \
--out assets/audio/voice/boss-line-final.mp3
mp3_44100_128, 0.5-2.5s, prompt influence 0.55-0.8.--loop, prompt influence 0.3-0.55.Report:
npx claudepluginhub bernatmv/ai-rules --plugin gamedev-threejsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.