unity-engineer

Implement Unity gameplay systems with ScriptableObject-first architecture and modular components.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Exia-thd/Digital-Nervous --skill unity-engineer-exia-thd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-engineer
Source: https://github.com/Exia-thd/Digital-Nervous/tree/main/skills/unity-engineer
Command: npx skills add https://github.com/Exia-thd/Digital-Nervous --skill unity-engineer-exia-thd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of creating maintainable, production-quality Unity games by enforcing robust architecture patterns and design principles. It prevents common pitfalls like Singleton abuse, tight coupling, and messy MonoBehaviours, enabling scalable, data-driven game development.

Core Features & Use Cases

  • ScriptableObject-First Design: Centralizes shared game data as SO assets, enabling designer-friendly tuning and decoupled communication via event channels.
  • Single Responsibility Components: Enforces modular, easy-to-maintain MonoBehaviours and prefab self-containment for scalable gameplay systems.
  • Production Pipeline Integration: Supports brownfield project migration, custom editor tooling, performance optimization, and automation via Unity-MCP tools. Use this Skill to implement gameplay systems from design specs, build UI, manage scenes, create editor tools, and optimize builds in Unity projects.

Quick Start

Ask the Unity Engineer to implement the gameplay systems from the Game Designer’s mechanic specs using ScriptableObject-first architecture and build a high-quality Unity game framework.

Frequently Asked Questions about unity-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build scalable Unity games without tightly coupling my MonoBehaviours?

To build scalable Unity games, you should enforce single responsibility components and use ScriptableObject-first design to centralize shared data, decoupling prefab communication and enabling designer-friendly tuning.

How do I use ScriptableObject event channels for decoupled communication in Unity?

Using ScriptableObject event channels for decoupled communication centralizes shared game data as SO assets, preventing Singleton abuse and messy MonoBehaviours while allowing modular gameplay systems to interact without tight coupling.

What is the best way to migrate a brownfield Unity project to a modular architecture?

The best way to migrate a brownfield Unity project to a modular architecture involves enforcing robust design principles, creating custom editor tooling, and applying ScriptableObject-first design to refactor tightly coupled MonoBehaviours.

Can I use this approach to build custom editor tools and optimize Unity builds?

Yes, you can use this approach to build custom editor tools and optimize Unity builds, as it supports production pipeline integration including brownfield project migration, editor tooling, and platform performance optimization.

Why does my Unity game framework suffer from Singleton abuse and how do I fix it?

Your Unity game framework suffers from Singleton abuse due to tight coupling, which you can fix by adopting a ScriptableObject-first architecture to decouple communication via event channels and enforce modular components.

Does this Unity architecture approach work with Unity-MCP automation tools?

Yes, this Unity architecture approach works with Unity-MCP automation tools, supporting integration with automation workflows to satisfy architecture validation, UI building, and production pipeline management.