unity-mobile-game-development
/unity-mobile-game-development
Use when building, restructuring, profiling, testing, or packaging a Unity mobile game in C# for Android or iOS; covers project architecture, scenes, prefabs, data, input, assets, saves, builds, and Unity-specific release evidence.
- Author
- peterbamuhigire ↗
- Repository
- chwezi-dev-engine ↗
- Licence
- MIT
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 2
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Use when building, restructuring, profiling, testing, or packaging a Unity mobile game in C# for Android or iOS; covers project architecture, scenes, prefabs, data, input, assets, saves, builds, and Unity-specific release evidence.
Original author description
Use when building, restructuring, profiling, testing, or packaging a Unity mobile game in C# for Android or iOS; covers project architecture, scenes, prefabs, data, input, assets, saves, builds, and Unity-specific release evidence.
How it works
- Prerequisites
- Use When
- Do Not Use When
- Required Inputs
- Workflow
- Quality Standards
- Anti-Patterns
- Outputs
- References
- Evidence Produced
SKILL.md preview
---
name: unity-mobile-game-development
description: Use when building, restructuring, profiling, testing, or packaging a Unity mobile game in C# for Android or iOS; covers project architecture, scenes, prefabs, data, input, assets, saves, builds, and Unity-specific release evidence.
metadata: {portable: true, compatible_with: [claude-code, codex]}
---
# Unity Mobile Game Development
Build a Unity game as modular, testable C# systems with reproducible mobile builds and measured target-device behaviour. Verify APIs and package guidance against the project's exact Unity version.
## Prerequisites
Load `world-class-engineering`, the approved game/system specification, and current official documentation for the pinned Unity version.
<!-- dual-compat-start -->
## Use When
- Creating or changing a Unity game, C# component, scene, prefab, ScriptableObject, mobile build, or Unity test.
- Migrating legacy UnityScript, old scene loading, input, UI, render-pipeline, networking, or platform code.
## Do Not Use When
- The project uses Godot; use `godot-mobile-game-development`.
- The task is engine-neutral design, art, audio, performance strategy, or release operations.
## Required Inputs
Repository and Unity version, render pipeline, target platforms/devices, package manifest, architecture, acceptance criteria, performance budgets, build/signing posture, and existing tests.
## Workflow
1. Inspect project settings, packages, assemblies, scenes, prefabs, assets, build scripts and tests before editing.
2. Record an ADR for costly choices: render pipeline, input, asset delivery, save model, scene flow, third-party SDKs and backend boundary.
3. Keep pure domain/gameplay logic separate from `MonoBehaviour`; use composition, explicit interfaces and event ownership.
4. Define a bootstrap/composition root, additive scene policy, prefab boundaries, data assets, lifetime rules and deterministic save identifiers.
5. Use the current supported input, UI, async loading, addressable-content and build paths verified for the pinned editor version.
6. Add edit-mode tests for pure logic, play-mode tests for integration, and physical-device smoke tests.
7. Profile development and release-like IL2CPP builds on the device panel; close with reproducible build and rollback evidence.
## Quality Standards
- Pin editor and package versions; commit text-serialised project assets and review dependency changes.
- Avoid hidden global state, stringly typed scene/object lookup, per-frame allocation, synchronous heavy I/O, and unbounded `Update` work.
- Keep secrets out of client builds and treat every analytics, ads, IAP or social SDK as a privacy, size, performance and failure dependency.
- Do not copy obsolete book APIs into production; translate the durable pattern into current official APIs.
## Anti-Patterns
- `Find` calls and singleton sprawl. Fix: explicit composition and scoped services.
- Business rules inside scene components. Fix: testable C# domain classes.
- One giant persistent scene. Fix: bounded additive scenes and ownership rules.
- Optimising only in Editor. Fix: device profiler and release-like build evidence.
- Upgrading packages casually. Fix: ADR, compatibility check, backup, tests and measured diff.
## Outputs
Unity architecture map; project/version manifest; system and scene specifications; implementation and tests; device profile; build pipeline; Unity-specific release evidence and residual-risk record.
## References
- [Unity project architecture](references/unity-project-architecture.md)
- [Legacy Unity migration and mobile build gates](references/unity-mobile-build-gates.md)
- [Unity 6 MCP and runtime UI notes](references/unity-6-mcp-and-runtime-ui-notes.md)
## Evidence Produced
| Category | Artifact | Format | Example |
| --- | --- | --- | --- |
| Correctness | Unity mobile vertical-slice evidence | Project/build output plus Markdown | scene flow, input, save, pause/resume, device profile, build, and failure check |
<!-- dual-compat-end -->
## Decision Rules
| Condition | Choice |
|---|---|
| Exact API/package behaviour is version-sensitive | Check official docs and package changelog before coding |
| Logic can run without Unity objects | Keep it in a plain C# assembly and unit-test it |
| Asset is large, optional or patchable | Evaluate addressable/remote delivery with offline failure handling |
| Plugin lacks maintenance, privacy or rollback evidence | Do not admit it |
## Read Next
Use `gameplay-systems-architecture`, `game-math-and-simulation`, `real-time-game-graphics`, `mobile-game-performance`, and `game-testing-polish` for their respective gates.
Files in this package (5)
- SKILL.md 5 KB
- agents/openai.yaml 1 KB
- references/unity-6-mcp-and-runtime-ui-notes.md 2 KB
- references/unity-mobile-build-gates.md 1 KB
- references/unity-project-architecture.md 1 KB
Versions
The database has no other skills named unity-mobile-game-development.
Database snapshot: 13.11.2026 · package version 37a4d3856fcc (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 81unity-editor-scripts-prefabs-builds
Use when the user builds a Unity game: C# scripts, scenes and prefabs, running and testing in the editor, profiling, importing assets, multiplayer basics, and building for PC, Android or iOS. - 100godot-mobile-game-development
Use when building, migrating, profiling, testing, or exporting a Godot mobile game for Android or iOS; covers scenes, nodes, resources, signals, GDScript/C#, saves, plugins, rendering, and export pipelines. - 100unity-development
Skill for communicating with Unity Editor via unity-agent-cli. Covers compilation checking, executing static methods, building UI prefabs, assigning assets, taking automated screenshots, verifying menus visually, and fixing errors autonomously. Use this skill whenever working on… - 100unity
Unity game engine guardrails, patterns, and best practices for AI-assisted development. Use when working with Unity projects, or when the user mentions Unity game development. Provides MonoBehaviour patterns, component architecture, physics, UI, and scripting guidelines. - 90scenoco-game
Make or change a browser game with SceNoCo — three.js scenes in TSX (no React) and Unity's behaviours, from the @scenoco-three npm packages. Use when asked to build a 2D or 3D web game with SceNoCo, three.js and Unity-style behaviours, to add a game to a React app, or to test or… - 100unity-dev
Use when implementing a Unity C# feature or fix, or when the user requests Unity architecture, implementation, review, or tests.