unity-architecture

Advises on Unity gameplay architecture, module boundaries, and execution order patterns.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/ethanJPope/Our-Main-Hackathon-Game --skill unity-architecture-ethanjpope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-architecture
Source: https://github.com/ethanJPope/Our-Main-Hackathon-Game/tree/main/.agents/skills/unity-skills/skills/architecture
Command: npx skills add https://github.com/ethanJPope/Our-Main-Hackathon-Game --skill unity-architecture-ethanjpope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unity projects often grow into tangled MonoBehaviour scripts with hidden dependencies, unpredictable startup order, and Update methods running on stale data. This Skill provides structured architecture guidance so you pick the smallest architecture that fits your project scope before writing lots of gameplay code. ## Core Features & Use Cases - Scoped Architecture Recommendations: Classifies your project as prototype, small game, or long-lived, then recommends 3-7 modules with clear responsibilities and a scene/bootstrap plan. - Execution Order and Guard Patterns: Provides concrete patterns for explicit startup ordering (single Bootstrap entry point, pull-don't-push, guarded Update methods) to eliminate random gameplay bugs. - Data Ownership Guidance: Clarifies what belongs in scene objects, ScriptableObjects, or plain C# classes, plus communication rules via direct refs, interfaces, events, or commands. - Use Case: Before building a new game's systems, ask for an architecture plan and receive a module breakdown, bootstrap strategy, and a do-now/skip-now list that avoids over-engineering. ## Quick Start Ask the assistant to recommend a Unity architecture for your project, describing its scope and core gameplay loop.

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 architecture?

Start by identifying your project scope (prototype, small game, or long-lived), then define the core loop and minimum runtime systems. Separate scene/bootstrap, gameplay logic, data/config assets, and presentation layers, keeping MonoBehaviours thin as composition bridges.

How to fix Unity script execution order problems?

Use a single Bootstrap script as the entry point that calls Init() on managers it creates, rather than relying on Script Execution Order settings. Reserve DefaultExecutionOrder attributes for load-bearing singletons only; needing more than 3-4 indicates an architecture problem.

When should I use ScriptableObjects in Unity?

Use ScriptableObjects for authored configuration and shared static data, not as a default dump for runtime state. Put reusable gameplay rules in plain C# classes and keep runtime state in scene objects or dedicated systems.

Why does my Unity Update method run with null data?

Update runs regardless of whether dependencies are ready, so missing guard clauses cause stale or null data access. Add early-return checks at the top of Update for initialization state, null dependencies, and gameplay pause flags.

When should I avoid a big architecture framework in Unity?

Avoid framework-heavy architecture for prototypes and small games where it slows iteration. Prefer a small architecture that can grow, with simple module boundaries over textbook SOLID layering, unless the project is genuinely long-lived.