About this skill

Problems It Addresses

Unity project pain is often not syntax, but pipeline, performance, architecture, and platform differences: URP / HDRP render bottlenecks, C# GC pressure, resource loading, multiplayer synchronization, mobile frame pacing, and CI builds. Generic answers can be fragmentary and miss Unity 6 LTS workflow constraints, as well as Profiler, asset pipeline, and platform limit perspectives.

How It Works

The skill turns Unity development tasks into actionable steps:
- Requirements analysis: define target platform, performance budget, render pipeline, and input constraints.
- Solution selection: compare URP, HDRP, DOTS, Job System, and Addressables.
- Implementation and verification: provide C# code, Shader Graph / HLSL ideas, Profiler checkpoints, and test plans, while checking frame rate, memory, and build size first.
- Boundary control: separate editor tools, runtime logic, package management, and cloud build workflows.

Limits

Best for Unity 6 LTS, C#, rendering, performance, architecture, and cross-platform deployment. Avoid it for non-Unity work or toolchains outside the game engine scope. It does not replace project design documentation, nor does it promise automatic asset processing, store certification, or third-party middleware integration.