Skill · Version 1.0.0

LÖVE audio and assets

Organizes reusable images and audio with clear loading and playback ownership. It distinguishes long streamed music from short effects and bounds simultaneous sounds, including during pause and scene changes.

love-audio-assets

See how it helps

When is it useful?

Use when sound effects interrupt one another or scene changes leak media.

What does it help you do?

Chooses streamed or static audio from content and concurrency.
Bounds overlapping voices and defines pause, stop and restart ownership.
Checks required assets before announcing readiness.

Try asking this

Our arcade game plays music and many explosion effects. Cap overlapping voices without cutting off important feedback, pause mid-track and restart the round. Simulate a missing sound file and show a useful error rather than declaring the scene fully ready.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

LÖVE — audio assets

Use when implementing LÖVE audio, streamed music, sprite sheets, loading or asset reuse.

Version and project gate

Inspect conf.lua and main.lua, LÖVE and Lua/LuaJIT versions, callback definitions, modules, filesystem identity, graphics/audio APIs, .love packaging and native extension dependencies. Distinguish color/API conventions across major releases. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.

Work

Choose static versus streamed Sources from the actual content and concurrency. Track playing-instance ownership and pause/stop rules. Reuse decoded images/quads/audio resources deliberately and bound overlapping voices. Publish readiness only after required assets exist and give missing assets a visible outcome.

Deliver

An asset/audio ownership contract and predictable play/pause/restart behavior. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.

Failure to prevent

Loading images or audio on every draw can churn memory; restarting a shared Source can interrupt another effect.

Acceptance scenario

Play overlapping effects, pause music, remove an owning scene and attempt a missing packaged sound without a silent success. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.

Scope and sources

This skill belongs to Lilt. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.

Task-specific official references

Included files 1

SKILL.md