audio-router_skill

Overview

This skill routes audio requests to the right specialty for playback, analysis, or audio-reactive visuals. It simplifies implementation by classifying intent, matching signal keywords, and combining skills when projects need multiple audio capabilities. Use it to decide whether to load players, extract frequency/beat data, or map audio to visuals.

How this skill works

The router inspects user requests for primary signals (playback, analysis, reactive) and assigns a confidence score. High-confidence matches route directly to a single skill; medium-confidence suggestions include supporting skills; low-confidence defaults to playback. For audio-visual projects it combines two or three skills (playback → analysis → reactive) and recommends integration patterns with post-processing, particles, GSAP, R3F, and shaders.

When to use it

• Implementing any audio functionality: music, SFX, ambient loops
• Building visualizers or audio-driven animations
• Adding beat detection, FFT, or waveform analysis
• Syncing visuals or effects to audio (beat, bass, treble)
• Designing multi-skill audio-visual pipelines

Best practices

• Classify intent by signal keywords: play, FFT, visualizer, beat, etc.
• Combine skills for complex projects: playback + analysis + reactive
• Default to audio-playback when intent is unclear
• Optimize analysis for performance: smaller FFT, smoothing
• Preload and reuse players to reduce latency and memory footprint

Example use cases

• Simple audio player: load, loop, crossfade background tracks
• Audio visualizer: playback → analyze spectrum → map to visuals
• Beat-synced animation: detect beats and trigger particle bursts
• Ambient soundscape: looping layers with crossfade and volume control
• Post-processing driven by audio: bass → bloom, highs → chromatic aberration