unity-architecture

Plan Unity module boundaries, scene bootstrap, and data ownership rules.

8|1|Updated Oct 7, 2025
One-click install
npx skills add https://github.com/Zzulin/unity-project01 --skill unity-architecture-zzulin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-architecture
Source: https://github.com/Zzulin/unity-project01/tree/main/URP1/Plugins/Unity-Skills-main/SkillsForUnity/unity-skills~/skills/architecture
Command: npx skills add https://github.com/Zzulin/unity-project01 --skill unity-architecture-zzulin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams and solo developers avoid messy, tightly-coupled Unity projects by providing concrete, scope-appropriate architecture guidance before writing large amounts of gameplay code. It reduces rework from poor module boundaries, unclear data ownership, and ill-considered communication patterns.

Core Features & Use Cases

  • Project tiering: Tailors recommendations for prototypes, small games, or long-lived projects.
  • Module recommendations: Suggests 3–7 modules with one-line responsibilities to keep code understandable and testable.
  • Scene & bootstrap planning: Explains where composition, initialization, and dependency wiring should occur.
  • Data ownership & communication rules: Advises what belongs in scene objects, ScriptableObjects, or plain C# classes and when to use direct references, interfaces, events, or commands.
  • Performance and priority guidance: Highlights likely hot paths, performance risks, and what to keep simple now versus what to abstract later.
  • Use case: Convert a fast prototype into a maintainable small-game structure or plan refactors for a long-lived live-service title.

Quick Start

Design a minimal, modular Unity architecture for a small 2D platformer with clear module responsibilities, data ownership rules, and a scene bootstrap plan.

Frequently Asked Questions about unity-architecture

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

FAQPage Schema
How do I structure a Unity project to avoid tightly coupled code and messy dependencies?

To structure a Unity project and avoid tightly coupled code, define clear module boundaries, establish data ownership rules, and use appropriate communication patterns like interfaces or events.

What is the best way to plan scene bootstrap and initialization in Unity?

The best way to plan scene bootstrap in Unity is to define where composition, initialization, and dependency wiring occur, ensuring scene objects and plain C# classes have clear responsibilities.

How do I refactor a Unity prototype into a maintainable architecture?

To refactor a Unity prototype into a maintainable architecture, tailor module recommendations to a small-game tier, separate data ownership, and highlight immediate engineering priorities to reduce rework.

When should I use ScriptableObjects versus plain C# classes for data ownership in Unity?

ScriptableObjects versus plain C# classes for data ownership in Unity depends on scope; ScriptableObjects work well for shared static data, while plain C# classes suit dynamic gameplay state and module communication.

How many modules should I create for clear separation of concerns in a small Unity game?

For clear separation of concerns in a small Unity game, create 3 to 7 modules with one-line responsibilities to keep code understandable, testable, and maintainable.

What are common performance risks when designing Unity gameplay architecture?

Common performance risks when designing Unity gameplay architecture involve ill-considered communication patterns and hot paths; identifying these early dictates what to keep simple now versus abstract later.