optimize-web — Claude Code skill for faster Unity Web builds

What optimize-web does

The skill drives the agent through Player Settings, compression, stripping and server setup for a Unity Web build. Before touching anything, the agent records a baseline of current behaviour and makes a restore point, so a later result can be traced to a specific change. Everything runs through the unity cli (unity command --format json) plus the unity-cli and unity-pipeline skills.

A topic map points to Unity docs on release-grade Player Settings, a C# editor script that applies them in one pass, removing unused packages, shader variant stripping, server compression headers and MIME types, and Wasm heap memory. The API side covers UnityEditor.PlayerSettings, UnityEditor.PlayerSettings.WebGL and UnityEditor.WebGL.UserBuildSettings, checked against the project's Unity version. That version comes from ProjectSettings/ProjectVersion.txt, package versions from Packages/packages-lock.json.

Docs are read from the editor's local Data/Documentation folder when it exists, otherwise from https://docs.unity.com/en-us/engine/<VERSION>/manual/. For com.unity.cloud.ktx, com.unity.addressables and com.unity.web.stripping-tool only .md files inside Library/PackageCache are allowed — other Library folders are off limits because the search gets slow. The agent also has to name the files it read and leave unrelated assets alone.