How do I install the Unity Architecture skill?

Run npx skillmds@latest add noah-zll/unity-architecture in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Unity Architecture safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Unity Architecture?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Unity Architecture free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Unity Architecture?

noah-zll (@noah-zll) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Unity Architecture by noah-zll — Agent Skill

Name: Unity Architecture
Rating: 4.2 (5 reviews)
Author: noah-zll

Unity Architecture

Gameplay and system architecture advisor for Unity. Use when users want module boundaries, scene design, SOLID structure, decoupling, or refactoring direction before writing code. Triggers: architecture, system design, how to structure, how to organize, module boundary, decouple, refactor, SOLID, 架构设计, 怎么组织代码, 模块划分, 代码结构, 解耦, 重构方向, 系统设计.

noah-zll Updated Sep 22, 2026

File contents

Unity Architecture Advisor

Use this before generating lots of gameplay scripts or when the user asks for a cleaner architecture.

Workflow

Identify scope: prototype, small game, or long-lived project.
Define the core loop and the minimum runtime systems needed.
Recommend the smallest architecture that fits the scope.
Separate:
- scene/bootstrap layer
- gameplay/domain logic
- data/config assets
- view/presentation layer
Call out what should stay simple now vs what is worth abstracting.

Output Format

When using this skill, structure the advice as:

Project tier: prototype / small-game / long-lived
Recommended modules: 3-7 modules with one-line responsibilities
Scene/bootstrap plan: where composition and initialization happen
Data ownership: what belongs in scene objects, ScriptableObjects, or pure C# classes
Communication rules: direct refs, interfaces, events, or commands
Performance risks: only the hot paths that matter
Do now / skip now: avoid over-engineering

Default Guidance

Prefer thin MonoBehaviour scripts as composition bridges.
Put reusable gameplay rules in plain C# classes when possible.
Use ScriptableObject for authored config and shared static data, not as a default dump for runtime state.
Keep dependencies explicit. Avoid hidden global state unless the project size clearly justifies a small service layer.
Favor simple module boundaries over framework-heavy architecture.

Guardrails

Mode: Both (Semi-Auto + Full-Auto) — advisory only, no REST skills

Do not start from a giant reusable framework unless the project truly needs it.
Do not add layers just to satisfy textbook SOLID wording.
Prefer a small architecture that can grow, not an impressive one that slows iteration.

Load Related Advisory Modules When Needed

Pattern choice: see ../patterns/SKILL.md
Async / Update / UniTask decisions: see ../async/SKILL.md
Inspector-facing field design: see ../inspector/SKILL.md
Script quality review: see ../scriptdesign/SKILL.md

---name: unity-architecturedescription: Gameplay and system architecture advisor for Unity. Use when users want module boundaries, scene design, SOLID structure, decoupling, or refactoring direction before writing code. Triggers: architecture, system design, how to structure, how to organize, module boundary, decouple, refactor, SOLID, 架构设计, 怎么组织代码, 模块划分, 代码结构, 解耦, 重构方向, 系统设计.---# Unity Architecture AdvisorUse this before generating lots of gameplay scripts or when the user asks for a cleaner architecture.## Workflow1. Identify scope: prototype, small game, or long-lived project.2. Define the core loop and the minimum runtime systems needed.3. Recommend the smallest architecture that fits the scope.4. Separate: - scene/bootstrap layer - gameplay/domain logic - data/config assets - view/presentation layer5. Call out what should stay simple now vs what is worth abstracting.## Output FormatWhen using this skill, structure the advice as:- Project tier: prototype / small-game / long-lived- Recommended modules: 3-7 modules with one-line responsibilities- Scene/bootstrap plan: where composition and initialization happen- Data ownership: what belongs in scene objects, ScriptableObjects, or pure C# classes- Communication rules: direct refs, interfaces, events, or commands- Performance risks: only the hot paths that matter- Do now / skip now: avoid over-engineering## Default Guidance- Prefer thin `MonoBehaviour` scripts as composition bridges.- Put reusable gameplay rules in plain C# classes when possible.- Use `ScriptableObject` for authored config and shared static data, not as a default dump for runtime state.- Keep dependencies explicit. Avoid hidden global state unless the project size clearly justifies a small service layer.- Favor simple module boundaries over framework-heavy architecture.## Guardrails**Mode**: Both (Semi-Auto + Full-Auto) — advisory only, no REST skills- Do not start from a giant reusable framework unless the project truly needs it.- Do not add layers just to satisfy textbook SOLID wording.- Prefer a small architecture that can grow, not an impressive one that slows iteration.## Load Related Advisory Modules When Needed- Pattern choice: see [`../patterns/SKILL.md`](../patterns/SKILL.md)- Async / Update / UniTask decisions: see [`../async/SKILL.md`](../async/SKILL.md)- Inspector-facing field design: see [`../inspector/SKILL.md`](../inspector/SKILL.md)- Script quality review: see [`../scriptdesign/SKILL.md`](../scriptdesign/SKILL.md)

Frequently asked questions