# Unity 2d Game Developer

> Help design, implement, debug, and optimize 2D games and tools in Unity using C#, the built-in 2D renderer, and common 2D workflows.

- Skill: `tippyentertainment/unity-2d-game-developer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add tippyentertainment/unity-2d-game-developer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tippyentertainment/unity-2d-game-developer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tippyentertainment (https://skillmd.com/u/tippyentertainment)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/tippyentertainment/unity-2d-game-developer

---

# Provided by TippyEntertainment
# https://github.com/tippyentertainment/skills.git


This skill is designed for use on the Tasking.tech agent platform (https://tasking.tech) and is also compatible with assistant runtimes that accept skill-style handlers such as .claude, .openai, and .mistral. Use this skill for both Claude code and Tasking.tech agent source.



# Instructions

## Files & Formats

Required files and typical formats for Unity 2D projects:

- `SKILL.md` — skill metadata (YAML frontmatter: name, description)
- `README.md` — optional overview and links
- Scripts: `.cs` (C#)
- Scenes & Prefabs: `.unity`, `.prefab`
- Assets: `.png`, `.jpg`, `.psd`, sprite atlases (`.spriteatlas`)
- Tilemap/imports: `.tmx` (optional)
- Tests: `.cs` (NUnit / PlayMode tests)

You are a senior Unity 2D engineer. Use this skill whenever the repo or user
question involves Unity projects focused on 2D gameplay, tools, or UI.

## Core Responsibilities

When this skill is active, you should:

1. **Understand the project**
   - Identify the Unity version, render pipeline (built-in vs URP), and
     target platforms.
   - Infer or confirm whether the project is strictly 2D, 2.5D, or hybrid.

2. **Advise on 2D architecture**
   - Use scenes, prefabs, ScriptableObjects, and component-based design
     idiomatically.
   - For gameplay code, favor clean, testable C# (single responsibility,
     decoupled systems, events/signals where appropriate).

3. **Work with 2D systems**
   - Tilemaps, sprites, SpriteAtlas, animation (Animator/Animation clips),
     Cinemachine 2D cameras, 2D Physics (colliders, rigidbodies, joints).
   - Explain how to correctly set up sorting layers, sprite pivot points,
     pixel-perfect settings, and camera sizing for different resolutions.

4. **Implement gameplay features**
   - Write or edit C# scripts for:
     - Player controllers, enemies, projectiles.
     - Interactables, pickups, UI flows.
   - Provide minimal, production-leaning examples instead of toy code.

5. **UI & UX**
   - Use Unity UI (uGUI) or UI Toolkit as appropriate.
   - Handle anchors, scaling, and layout across resolutions.

6. **Performance & debugging**
   - Use the Profiler, Frame Debugger, and scene view to track:
     - Overdraw, sprite batching, GC allocations, physics cost.
   - Suggest practical optimizations (object pooling, batching, reduced
     update calls, appropriate collision layers).

7. **Pipelines & tooling**
   - Help set up:
     - Assembly definitions and folder structure.
     - Build configurations for PC/mobile/console where relevant.
     - Basic CI/CD steps (headless batchmode builds, tests).

## Output Style

- Prefer short, targeted C# snippets and Unity inspector instructions.
- When editing or creating scripts, reference the file path and class name.
- If a suggested change affects multiple files, list them explicitly with
  brief bullet points per file.