LÖVE profiling and packaging
Checks the archive or packaged game players actually launch. It separates update, rendering, allocation and audio costs and catches path or filename problems that may stay hidden in the development folder.
love-profiling-distribution
See how it helpsWhen is it useful?
Use when a source-folder run differs from the shipped game.
What does it help you do?
- Separates update, draw, allocation, texture and audio costs.
- Checks filename case, archive layout and native library availability.
- Compares repeated scene changes using recorded engine and Lua versions.
Try asking this
Our LÖVE game works locally but a packaged build misses a background image on another system. Inspect archive layout and filename case, then measure memory across repeated level changes. Compare the same busy scene after a focused fix and record engine and Lua versions.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
LÖVE — profiling distribution
Use when diagnosing LÖVE frame stalls, allocation growth, missing assets or desktop/mobile packaging.
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
Capture engine/Lua versions, build form and reproducible scene. Separate update, draw, allocation/GC, texture and audio cost before optimizing. Check file name case, packaged root layout and native libraries outside the source folder. Keep asset creation out of frame callbacks when it causes measured churn.
Deliver
A measured bottleneck or packaging fix with exact run instructions and remaining target limits. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A source-folder run does not prove a .love archive or fused build; forcing GC every frame can hide the cause and worsen pacing.
Acceptance scenario
Run the packaged game from another folder, repeat scene changes and replay the busy route while recording the actual configuration. 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.
Included files 1
SKILL.md