hashgraph-online/awesome-codex-plugins / plugins/AUN-PN/unity-agent-workflows/skills/unity-agent-workflows
unity-agent-workflows
VerifiedUse for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first content changes, validation, cleanup proof, or durable workflow rules. Best when agents must prove the actual folder/module/scene/prefab/runtime owner before editing, especially runtime UI, generated assets, code graphs, tutorial/state flows, guided selection/action flows, overlay/dim source-bound mistakes, coordinate conversions, focus/highlight/marker/HUD alignment, predictive lead aiming, ballistic trajectories, spatial IoU verification, or repeated "fix still not visible" failures.
references/project-structure-discovery.md
View on GitHub# Project Structure Discovery
## Purpose
Use before architecture routing, new files/classes, cross-module calls, or broad Unity edits. Learn only the relevant live project structure; do not force this skill's sample layout or scan the whole repo by default.
Output: focused structure map in task notes, a short `UNITY_STRUCTURE.md` index, or split focused files when the user wants persistent docs.
## Discovery Inputs
Read only what exists and only what the task needs:
- Always-read: `AGENTS.md`, relevant `README.md`/architecture docs, existing focused structure maps.
- UI/runtime bug: scene/prefab path, presenter/controller, Canvas/TMP/safe-area code.
- Runtime/content feature: owning runtime module, related data/config, event/contract path.
- Content/balance: ScriptableObjects/config/localization that own the values.
- Assembly/refactor: folders, namespaces, `.asmdef`, graph edges for touched modules.
- Cleanup: code refs, YAML/GUID refs, Resources/addressable paths.
- Code graph reports only when routing or dependency proof depends on them: graph report, graph wiki, `graph.json`, or equivalent.
Do not invent folders or layer names that are not visible in the repo.
Do not scan unrelated categories just to fill a template.
## Serialized Wiring Scan
Code search alone is insufficient. Before unused/deletion/rename/routing claims, scan Unity serialized surfaces that can call/reference code without C# callsites.
Use for refactor, deletion, rename, routing, dead-code claims, owner proof, button/menu actions, animation flow, scene/prefab impact:
- script `.meta` GUID -> `.unity`, `.prefab`, `.asset`, `.controller`, `.anim`, and relevant generated/imported asset references
- `UnityEvent` persistent calls such as `Button.onClick`, `Toggle.onValueChanged`, timeline/signals, or custom serialized events
- `AnimatorController` states, transitions, parameters, blend trees, and animation events that reference method names or state keys
- prefab/scene back-references from serialized assets to MonoBehaviours, components, fields, and object references
- `Resources.Load`, Addressables/resource keys, registry/factory paths, and ScriptableObject-driven bindings when present
Treat `rg` over `.cs` as code evidence only. A dead-code, unused-asset, or safe-rename conclusion needs serialized wiring evidence too, or it must be reported as unproven.
## Teach Command Contract
```text
$unity-agent-workflows. Teach
```
Contract:
1. Create or refresh a short `UNITY_STRUCTURE.md` index.
2. Auto-split detailed structure into focused files by category.
3. Create a focused file only when the category is present, useful, or requested.
4. Never dump every folder, scene, graph node, or raw search result into one file.
```text
UNITY_STRUCTURE.md
UNITY_STRUCTURE.ui.md
UNITY_STRUCTURE.runtime.md
UNITY_STRUCTURE.content.md
UNITY_STRUCTURE.assemblies.md
UNITY_STRUCTURE.cleanup.md
```
Each focused file must include:
```text
When to read:
Primary paths:
Runtime/source owners:
Data/config owners:
Cross-module routes:
Validation hints:
Do-not-touch:
Open gaps:
```
## File Router
| Task | Read |
|---|---|
| UI, HUD, menu, safe area, TMP, visible target | `UNITY_STRUCTURE.md`, `UNITY_STRUCTURE.ui.md` |
| Runtime behavior, scene objects, interactions, abilities, objectives | `UNITY_STRUCTURE.md`, `UNITY_STRUCTURE.runtime.md` |
| Balance, localization, ScriptableObjects, config | `UNITY_STRUCTURE.md`, `UNITY_STRUCTURE.content.md` |
| New files, refactor, asmdef, namespace, dependency | `UNITY_STRUCTURE.md`, `UNITY_STRUCTURE.assemblies.md` |
| Deletion, cleanup, generated files, Resources/addressables | `UNITY_STRUCTURE.md`, `UNITY_STRUCTURE.cleanup.md` |
If a task spans categories, read the index first, then the smallest needed focused maps.
## Structure Map
Capture this before structural edits:
```text
Project root:
Unity version/source:
Repo instructions:
Existing structure docs:
Scripts roots:
Observed module folders:
Observed namespaces:
Assemblies/asmdefs:
Scene roots:
Prefab roots:
Bootstrap/composition roots:
Content/data roots:
UI roots:
Asset/art roots:
Generated/cache/build-output roots:
Runtime owner patterns:
Cross-module communication patterns:
Validation commands found:
Do-not-touch areas:
Open uncertainty:
```
## Routing Rules
- Route to the repo's existing owner first.
- Match the repo's folder, namespace, assembly, scene, prefab, and content patterns.
- If the repo has no clear module structure, patch the proven owner in place and keep new code beside the closest live owner.
- If the repo has a modular structure, use the project's own module names and dependency direction.
- If docs disagree with live code, treat live code as source of truth and report the mismatch.
- If multiple owners are equally plausible and the choice changes runtime behavior, ask one focused question before editing.
## Optional Persistent Context
If the user wants a teach/document flow, keep `UNITY_STRUCTURE.md` as a short index:
```text
Project Identity
Known Structure Maps
Do-Not-Touch Areas
Validation Notes
Open Gaps
```
Rules:
- Prefer focused maps over one huge file.
- Keep it descriptive, not prescriptive.
- Use exact paths from the repo.
- Mark inferred facts as inferred.
- Do not copy huge graphs or raw file dumps.
- Refresh only the stale area when structure changes meaningfully.
## Fallback Pattern
If a project has no structure docs and no obvious layering, use local ownership:
```text
new behavior -> beside the proven runtime owner
shared data -> beside the existing data/config path
shared contract -> smallest existing boundary or local interface near the caller
visual/UI -> beside the scene/prefab/presenter that owns the visible layer
```
Core/Systems/Features is only a sample pattern. Use it only when the repo already follows it or the user explicitly asks to migrate toward it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |