optimize-audio

Critical Rules Do not make changes before reporting findings to the user Follow steps in strict order; never jump ahead STOP at every WAIT checkpoint and await the user's response before continuing Quality is more important than speed: measure before and after every change Always verify results in a device build; Editor audio stats are indicative only 0. Set up the execution path Every C# step below runs inside a live Editor through the Unity CLI. The unity-cli skill owns getting you there — installing the CLI, confirming a connected Editor, adding the project's com.unity.pipeline package, telling a genuinely absent Editor apart from one stuck in Safe Mode, and discovering the Editor's command catalog. Follow it first; don't re-derive any of it here. Two things it can't know for you: Show more Installs 957 Repository unity-technolog…s/skills GitHub Stars 491 First Seen 13 days ago Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass