unity-dev

Solid

Start Unity C# development workflow with architecture, implementation, review, and testing phases

AI & Automation 6 stars 0 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
28
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Unity Development Workflow You are orchestrating a complete Unity C# development workflow. Follow these phases systematically. ## Phase 1: Discovery First, understand the project and task: 1. **Check for Unity project markers:** - `*.csproj` files - `ProjectSettings/` folder - `Assets/` folder - `*.unity` scene files 2. **Read existing architecture:** - Check for `CLAUDE.md` or project documentation - Look at existing code patterns in `Assets/Scripts/` - Identify assembly definitions (`.asmdef` files) 3. **Clarify requirements** if task is ambiguous using AskUserQuestion ## Phase 2: Architecture Use the `unity-architect` skill knowledge to: 1. **Design component hierarchy** - MonoBehaviour structure, interfaces 2. **Create test stubs** - EditMode + PlayMode test cases 3. **Generate Mermaid diagrams** - Class, sequence, state machine 4. **Define contracts** - Interfaces before implementations Present the architecture to the user for approval before implementing. ## Phase 3: Implementation Use the `unity-coder` skill knowledge to implement: 1. Follow Unity C# coding guidelines precisely 2. Implement against the test stubs created in Phase 2 3. Use the `unity-tests-run` skill to run tests continuously as you implement 4. Use proper serialization attributes (`[SerializeField]`, `[field:SerializeField]`) ## Phase 4: Review Spawn the `unity-reviewer` agent to perform Unity-specific code review: - MonoBehaviour lifecycle issues - Serialization ...

Details

Author
DmitriyYukhanov
Repository
DmitriyYukhanov/claude-plugins
Created
6 months ago
Last Updated
4 days ago
Language
Shell
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category