S
sgonzalezrozo/unity-architecture-agents
Architecture rules and a working process for AI coding assistants on Unity projects.
updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
- Star count
- 0 ★ · sgonzalezrozo/unity-architecture-agents · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 2 sources
- Score
- score 203 · 2 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
sgonzalezrozo/unity-architecture-agents;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# Unity Architecture Agents
Excerpted from the repository README (abridged)
Architecture rules and a working process for AI coding assistants on Unity projects.
Unity Architecture Agents is a free, open-source AGENTS.md and CLAUDE.md rule set for AI coding agents on Unity 6 projects. It gives agents a strict MVC architecture for uGUI, Roslyn analyzers that turn the rules into compile errors, a batch-mode verify script, and a Claude Code hook that won't let an agent finish with a broken build. Templates cover Cursor, GitHub Copilot and Rider AI Assistant. It works with Unity MCP servers and the Unity CLI.
## What's included
| File | Purpose |
| AGENTS.md | Entry point: stack, philosophy and where to read next |
| Developer overview | One-file summary for human developers |
| Agent workflow | Task classification, plan format, checklist, Definition of Done and Git |
| MVC | How Models, Views and Controllers work together |
| Feature structure | Folders, naming, and screen composition |
| Dependency injection | Bindings, installers and references |
| Backend integration | How features talk to a backend |
| UI patterns | Clickable elements, visual states, tabs, lists and layouts |
| Optional packages | How an agent detects optional packages and adapts its code |
| C# standards | Style, performance, async, logging and tests |
| Editor tools | How an agent verifies its work with Unity MCP, the Unity CLI or verify.sh |
| Examples | Three complete features with invented names: a backend feature, custom input and a filtered list |
| Templates | .editorconfig, Copilot, Cursor and Rider rules, verify.sh and a Claude Code Stop hook |
| Analyzers | Roslyn analyzers that turn the mechanical rules into compile errors |
## How the process scales
| Request | Process |
| Question, explanation, review | Answer directly |
| Small change inside existing classes | Make the change and summarize it |
| New feature, screen, class family or refactor | Plan first, wait for approval |
Before returning code, the agent runs the pre-response checklist. The analyzers turn the mechanical items into compile errors.
## Use it in a project
Add this repository as a Git submodule. Unity ignores a folder that starts with a dot, so .ai/ is never imported and creates no .meta files.
bash
git submodule add https://github.com/sgonzalezrozo/unity-architecture-agents.git .ai
Assistants look for their instructions at the project root, and a submodule can only add a folder. Add these two small files at the root to point to it.
AGENTS.md:
markdown
# AGENTS.md
All rules live in the .ai submodule. Read .ai/AGENTS.md completely, then open only the document it points to.
If .ai/ is empty, run git submodule update --init.
CLAUDE.md:
text
@.ai/AGENTS.md
Keep rules that only apply to one project in that project's root AGENTS.md.
### Copilot, Rider and code style
These tools only read files from fixed paths in your project, so copy the ones you use:
bash
cp .ai/templates/.editorconfig .
mkdir -p .github .aiassistant/rules
cp .ai/templates/copilot-instructions.md .github/
cp .ai/templates/rider-project-rule.md .aiassistant/rules/project.md
mkdir -p .cursor/rules
cp .ai/templates/cursor-rule.mdc .cursor/rules/unity-architecture.mdc
Commit these copies in your project. In Rider, set the rule's type to Always.
Unity Architecture Agents is a free, open-source AGENTS.md and CLAUDE.md rule set for AI coding agents on Unity 6 projects. It gives agents a strict MVC architecture for uGUI, Roslyn analyzers that turn the rules into compile errors, a batch-mode verify script, and a Claude Code hook that won't let an agent finish with a broken build. Templates cover Cursor, GitHub Copilot and Rider AI Assistant. It works with Unity MCP servers and the Unity CLI.
## What's included
| File | Purpose |
| AGENTS.md | Entry point: stack, philosophy and where to read next |
| Developer overview | One-file summary for human developers |
| Agent workflow | Task classification, plan format, checklist, Definition of Done and Git |
| MVC | How Models, Views and Controllers work together |
| Feature structure | Folders, naming, and screen composition |
| Dependency injection | Bindings, installers and references |
| Backend integration | How features talk to a backend |
| UI patterns | Clickable elements, visual states, tabs, lists and layouts |
| Optional packages | How an agent detects optional packages and adapts its code |
| C# standards | Style, performance, async, logging and tests |
| Editor tools | How an agent verifies its work with Unity MCP, the Unity CLI or verify.sh |
| Examples | Three complete features with invented names: a backend feature, custom input and a filtered list |
| Templates | .editorconfig, Copilot, Cursor and Rider rules, verify.sh and a Claude Code Stop hook |
| Analyzers | Roslyn analyzers that turn the mechanical rules into compile errors |
## How the process scales
| Request | Process |
| Question, explanation, review | Answer directly |
| Small change inside existing classes | Make the change and summarize it |
| New feature, screen, class family or refactor | Plan first, wait for approval |
Before returning code, the agent runs the pre-response checklist. The analyzers turn the mechanical items into compile errors.
## Use it in a project
Add this repository as a Git submodule. Unity ignores a folder that starts with a dot, so .ai/ is never imported and creates no .meta files.
bash
git submodule add https://github.com/sgonzalezrozo/unity-architecture-agents.git .ai
Assistants look for their instructions at the project root, and a submodule can only add a folder. Add these two small files at the root to point to it.
AGENTS.md:
markdown
# AGENTS.md
All rules live in the .ai submodule. Read .ai/AGENTS.md completely, then open only the document it points to.
If .ai/ is empty, run git submodule update --init.
CLAUDE.md:
text
@.ai/AGENTS.md
Keep rules that only apply to one project in that project's root AGENTS.md.
### Copilot, Rider and code style
These tools only read files from fixed paths in your project, so copy the ones you use:
bash
cp .ai/templates/.editorconfig .
mkdir -p .github .aiassistant/rules
cp .ai/templates/copilot-instructions.md .github/
cp .ai/templates/rider-project-rule.md .aiassistant/rules/project.md
mkdir -p .cursor/rules
cp .ai/templates/cursor-rule.mdc .cursor/rules/unity-architecture.mdc
Commit these copies in your project. In Rider, set the rule's type to Always.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/sgonzalezrozo-unity-architecture-agents/)
- Source
- github · https://github.com/sgonzalezrozo/unity-architecture-agents
- Browse by field
- Open source
- Listed by
- 2 independent sources
- added
- today
More entries
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.