audio-debugger-ambient-vs-gig

Trace ambient and gig audio playback timing in web audio React projects.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/DaFum/neurotoxic-game --skill audio-debugger-ambient-vs-gig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audio-debugger-ambient-vs-gig
Source: https://github.com/DaFum/neurotoxic-game/tree/main/.agents/skills/audio-debugger-ambient-vs-gig
Command: npx skills add https://github.com/DaFum/neurotoxic-game --skill audio-debugger-ambient-vs-gig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug ambient vs gig playback behavior (full tracks vs excerpts, start/stop timing). Use when audio stutters, plays incorrectly, or needs additional logging.

Core Features & Use Cases

  • Trace playback initialization in AudioManager.js and see how ambient playback starts with full MIDI tracks
  • Validate that gig playback starts at configured offsets and stops at expected durations
  • Add targeted logging around start/stop calls, timing offsets, and duration scheduling
  • Verify AudioContext initialization on user gesture and ensure compatibility with the web audio environment
  • Cross-check rhythm/songs metadata offsets against the data definitions to catch drift

Quick Start

Trace the ambient vs gig playback flow in the codebase and verify that start times and offsets align with the configuration.

Frequently Asked Questions about audio-debugger-ambient-vs-gig

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug audio playback timing and sequencing issues in a React web audio project?

To debug audio playback timing in a React web audio project, you can trace the playback flow, validate configured offsets against song definitions, and add targeted logging around start and stop calls to catch timing drift.

Why does my web audio stutter or play incorrectly when switching between ambient MIDI tracks and scheduled gig excerpts?

Audio playback stutters or plays incorrectly when configured offsets drift from song definitions or AudioContext initialization fails. Tracing the ambient vs gig playback flow validates precise start/stop timing and duration scheduling to resolve the issue.

How do I verify AudioContext initialization on user gesture for MIDI playback?

Verifying AudioContext initialization on user gesture involves checking the web audio environment compatibility and tracing playback initialization in AudioManager to ensure ambient MIDI playback starts correctly.

What is the best way to add targeted logging for audio start/stop calls and timing offsets?

The best way to add targeted logging for audio start/stop calls is to cross-check rhythm and songs metadata offsets against data definitions, logging timing events to catch drift and validate duration scheduling.

Does this audio debugging approach work with scheduled excerpts and full MIDI tracks?

Yes, this audio debugging approach works with scheduled excerpts and full MIDI tracks by validating that gig playback starts at configured offsets, stops at expected durations, and ambient playback starts with full tracks.