datnt-cell Unity Architecture Advisory
Part of the Unity Skills plugin. These modules are documentation-only — they define no REST skills and don't require the Unity Skills protocol below.
If the task also needs Editor automation (creating files, querying the scene), use this quick reference:
Unity Skills protocol (quick reference)
This plugin talks to the Unity Editor through a local REST server. Before the first skill call in a session:
GET /health— discover the server (it binds a port in8090–8100). ReadcurrentMode("approval"/"auto"/"bypass") andsurfaceProfile(full/guide/noSceneAuthoring) — confirmprojectNamematches the project you're editing.- Under
approvalmode, the first write to aFullAutoskill returnsMODE_RESTRICTEDand needs a user grant; underauto/bypasswrites execute directly.
dryRun gate: before executing any skill whose exact parameters you don't already hold, call POST /skill/<name>?mode=dryRun and iterate until the response says valid:true — never guess parameters from a skill name alone. Then execute the same call without ?mode=dryRun.
Batch execution: when touching 2+ objects, prefer POST /skills/batch ({"steps":[{"skill","args"}],"continueOnError":false}, up to 50 steps per call, also supports ?mode=dryRun) over repeated single-item calls.
Error codes:
| Code | Meaning |
|---|---|
MODE_RESTRICTED / MODE_FORBIDDEN |
Needs a user grant, or needs Bypass/Allowlist. |
SURFACE_EXCLUDED |
Hidden by the current surfaceProfile — a configuration boundary, not a failure; don't retry or route around it. |
MISSING_PARAM / TARGET_NOT_FOUND |
Bad or unresolvable arguments — dryRun for the schema, locate the target first. |
For the full protocol detail, error code catalog, and guide-mode manual-* docs, optionally install the unity-core plugin — it's not required, this summary covers what you need for this skill.
Modules in this skill
| Module | Description | Doc |
|---|---|---|
| project-scout | Inspect existing project | modules/project-scout/SKILL.md |
| architecture | Plan system boundaries | modules/architecture/SKILL.md |
| adr | Record tradeoffs | modules/adr/SKILL.md |
| performance | Review hot paths | modules/performance/SKILL.md |
| blueprints | Small-game blueprints | modules/blueprints/SKILL.md |
| scene-contracts | Define scene wiring | modules/scene-contracts/SKILL.md |
| inspector | Design authoring UX | modules/inspector/SKILL.md |
Routing
Start with project-scout when picking up an unfamiliar project — it establishes the baseline the other advisories build on. Use architecture and adr together when a design decision needs both a plan and a recorded rationale. performance and scene-contracts are useful before large automation passes from other unity-* skills, to avoid baking in a design that needs rework.
None of these modules call REST endpoints — they're read/write-to-docs guidance you produce directly, not automation you dispatch through the Unity Editor server.