cuozg/unity-code
skills/unity-code/SKILL.md
Unified Unity runtime C# coding skill — write, extend, or refactor runtime code using code-standards as the single source of truth for patterns and conventions. Integrates with Unity MCP for mandatory console verification after every code change. Auto-triages: Quick (single-file MonoBehaviour, ScriptableObject, interface, enum, struct, helper), Deep (multi-file features, services, state machines, refactors spanning 2+ classes). MUST use for ANY Unity runtime code request — creating scripts, adding components, implementing features, building systems, refactoring, or cleanup. Triggers: "write a script," "add a component," "build a system," "implement feature," "refactor," "clean up," "simplify." Do not use for performance optimization (unity-optimize), Editor scripts (unity-editor), UI Toolkit (unity-uitoolkit), tests (unity-test-unit), or debugging (unity-debug).
$ install --global
skillsauthnpx skillsauth add cuozg/oh-my-skills unity-codeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 13, 2026, 2:47 AM189.6s5 files scanned
SKILL.md
- name:
- unity-code
- description:
- >
- Auto-triages:
- Quick (single-file MonoBehaviour, ScriptableObject, interface, enum,
- Triggers:
- write a script," "add a component," "build a system," "implement feature,
- author:
- kuozg
- version:
- 5.0
unity-code
Detect scope, load code-standards, discover local patterns, implement complete runtime code, verify via Unity console.
Step 1 — Detect Mode
| Signal | Mode |
|--------|------|
| One .cs file, narrow runtime edit, single component/type | Quick |
| 2+ files, new feature/system, cross-class refactor | Deep |
| "Clean up," "simplify," behavior unchanged | Quick or Deep (by file count) |
State triage: "This is [mode] — [reason]."
Step 2 — Load References (In Order)
- Routing table —
read_skill_file("unity-code", "references/reference-routing.md")— identifies 1–3 code-standards files for this task - Mode workflow —
read_skill_file("unity-code", "references/quick-mode.md")orreferences/deep-mode.md - Code standards —
read_skill_file("unity-standards", "references/code-standards/<file>.md") - MCP tools (first use per session) —
read_skill_file("unity-standards", "references/other/unity-mcp-routing-matrix.md")
Code-standards = single source of truth for all patterns, naming, conventions. Mode reference = procedural workflow only.
Step 3 — Discover Local Patterns
Before writing any code, read target file + 1–2 nearby files. Capture:
- Namespace pattern (
Company.Project.Feature) - Field style (
_camelCasevsm_camelCase) - Serialization (
[SerializeField]vs[field: SerializeField]auto-props) - Component caching (
Awake()GetComponent vs lazy properties) - Event pattern (C# events, UnityEvent, SO channels)
- DI approach (constructor injection,
[Inject], Inspector drag-drop)
Local style wins. Match what neighboring files do.
Step 4 — Execute
- Quick: Qualify → Discover → Implement → Verify → Handoff
- Deep: Qualify → Discover → Plan → Implement → Verify → Handoff
Step 5 — Console Verification (MANDATORY — No Exceptions)
After every code change:
lsp_diagnosticson all changed filesUnity.ReadConsolevia Unity MCP- Errors (CS####) → fix immediately, repeat · Warnings → note in handoff · Clean → handoff
Fallbacks: MCP only → note LSP limitation · LSP only → note "Console verification unavailable — verify in Unity Editor" · Both unavailable → manual review, note both limitations.
Never declare complete without console verification or explicit fallback note.
Rules
- Code-standards is the single source of truth — do not invent patterns
- Local style wins over standards
- Never bulk-load all code-standards — routing table picks 1–3
- Never leave
TODO, stubs, or half-wired code - One type per file
- Bug fixes: minimal diff, no mixed refactors
- Ambiguity → simplest implementation; state assumption in handoff
Escalation
| To | When |
|----|------|
| unity-editor | Target is editor domain |
| unity-optimize | User wants performance optimization |
| Quick → Deep | Work requires a second file |
| Deep → Quick | Plan reveals single-file scope |
Related Skills
cuozg/unity-image-gen
tools
VerifiedTrustedCommunity
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
4SKILL.mdUpdated May 29, 2026
cuozg/unity-technical
tools
VerifiedTrustedCommunity
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
4SKILL.mdUpdated May 26, 2026
cuozg/unity-mcp-orchestrator
tools
VerifiedTrustedCommunity
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
4SKILL.mdUpdated May 21, 2026
cuozg/goal-todo
development
VerifiedTrustedCommunity
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.
4SKILL.mdUpdated May 21, 2026