agentleFS
Sign inStart free
mtarcuremtarcure/claude-vibe-squad/.agents/skills/audio-event-map-authoring/SKILL.md

audio-event-map-authoring

Skill220 starsChanged 18 days agoMITView on GitHub

Use when an adaptive game-audio design must become an engine-ready audio-event-map.json: define stable event and parameter IDs, cue transitions and cancellation, fallbacks, budgets, formats, and transition tests. Not for designing adaptive-audio behavior, rendering assets, or writing engine integration.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add test scenarios that exercise transitions and cancellations.

    line 17
  2. Distinctive:

    Every event has an explicit fallback.

    line 21
  3. Distinctive:

    Test scenarios cover transition and cancellation behavior.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audio Event Map Authoring

Author the typed game-event → audio-cue contract (audio-event-map.json) that hands an interactive-audio design to the engine.

Steps

  1. Enumerate the game events that drive audio; assign each a unique, stable event ID.
  2. For each event, define the cue, transition/cancellation behavior, parameter IDs, and units/ranges.
  3. Specify a missing-cue fallback for every event so the runtime never silently fails.
  4. Record memory/voice-count/streaming budgets and loop/loudness/format requirements.
  5. Version the schema and name the middleware/runtime target.
  6. Add test scenarios that exercise transitions and cancellations.

Acceptance

  • Event and parameter IDs are unique and stable; schema version present.
  • Every event has an explicit fallback; budgets and format requirements stated.
  • Test scenarios cover transition and cancellation behavior.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free