From meta-vr
Analyzes Unity projects targeting Meta Quest and Horizon OS, generating and maintaining .agent-docs/ knowledge base for structure, scenes, scripts, prefabs, and systems. Use for scans, explanations, or updates.
npx claudepluginhub meta-quest/agentic-tools --plugin meta-vrThis skill uses the workspace's default tool permissions.
Analyze, document, and maintain a living knowledge base of a Unity project's structure, optimized for AI agent comprehension. Output lives in `.agent-docs/` as source-control-friendly markdown files.
CLI for reading scenes/prefabs/assets, small updates, deletes, and utilities in Unity projects without live editor bridge. Emits structured JSON; boot with setup/status.
Organizes Unity project paths for code, content, tests, editor tooling, and build assets to keep them discoverable and maintainable. Use when structure drifts, teams or plugins are added, or content scales.
Automates Unity Editor from terminal via ucp CLI over WebSocket/JSON-RPC: scenes, GameObjects, assets, prefabs, builds, tests, packages, debugging. Use for headless project inspection, modification, and workflows.
Share bugs, ideas, or general feedback.
Analyze, document, and maintain a living knowledge base of a Unity project's structure, optimized for AI agent comprehension. Output lives in .agent-docs/ as source-control-friendly markdown files.
This skill operates in four modes. Determine which mode to use based on context:
Trigger: .agent-docs/ directory does not exist or .agent-docs/index.md does not exist.
Trigger: User asks to update docs, or AI agent has made structural changes (new scenes, scripts, prefabs, systems). Default update mode.
Important: Incremental updates are part of implementation, not a separate step. When creating or modifying scripts, prefabs, or assets, update the corresponding .agent-docs/ files in the same pass before moving on to the next task.
Trigger: User explicitly requests a full rescan (e.g., "rescan project", "full project analysis").
Trigger: User asks about the project structure or how a system/feature works (e.g., "what does this project do", "how does the ball system work", "project structure", "load project analysis"). Only use this mode when .agent-docs/ exists. This mode is read-only — do not modify docs.
README.md, CHANGELOG.md, and any docs in Documentation/ folderPackages/manifest.json to understand all included packagesAssets/**/*.unityAssets/**/*.asmdef.prefab filesProjectSettings/ProjectVersion.txtBefore documenting, ask the user about anything that is not clear from the code or docs alone. Examples:
Only ask about genuinely ambiguous items. If something is clear from naming, folder structure, or code inspection, document it directly.
For each category below, create or update the corresponding sub-document:
.agent-docs/project-overview.md).agent-docs/scenes/)Create one file per scene (e.g., .agent-docs/scenes/startup.md).
For each scene document:
Create a scene flow diagram in .agent-docs/scenes/_flow.md using mermaid:
graph LR
Startup --> MainMenu --> Gameplay
.agent-docs/systems/)Identify logical systems (networking, UI, audio, input, gameplay, etc.) and create one file per system.
For each system document:
.agent-docs/prefabs/)Group or document individually based on clarity:
.agent-docs/prefabs/ui-elements.md).agent-docs/prefabs/player-rig.md)For each prefab/group:
.agent-docs/assets/)Document non-script, non-prefab assets adaptively:
.agent-docs/scripts/)Scripts are self-documenting through code. Here, document usage context only:
Create or update .agent-docs/index.md as the main entry point:
# [Project Name] — Agent Documentation
> Auto-generated project knowledge base for AI agent comprehension.
> Last updated: YYYY-MM-DD
## Quick Context
[2-3 sentence project summary]
## Document Map
- [Project Overview](project-overview.md)
- Scenes
- [Scene Flow](<scenes/_flow.md>)
- [SceneName](<scenes/scene-name.md>)
- ...
- Systems
- [SystemName](<systems/system-name.md>)
- ...
- Prefabs
- [PrefabGroup](<prefabs/group-name.md>)
- ...
- Assets
- [AssetGroup](<assets/group-name.md>)
- ...
- Scripts
- [ScriptArea](<scripts/area-name.md>)
- ...
## Runtime Flow
[Brief description of app lifecycle from launch to gameplay]
Create .agent-docs/_config.md:
---
last_full_scan: YYYY-MM-DD
last_update: YYYY-MM-DD
documented_systems:
- system-name-1
- system-name-2
documented_scenes:
- scene-name-1
- scene-name-2
documented_prefab_groups:
- group-name-1
- group-name-2
---
.agent-docs/_config.md and .agent-docs/index.mdPackages/manifest.json.agent-docs/index.md if new docs were added or removedlast_update and the documented lists in .agent-docs/_config.mdDo NOT rewrite docs that haven't changed.
.agent-docs/index.md exists — if not, skip (no docs to ingest).agent-docs/index.md to get the document map and quick contextproject-overview.mdsystems/balls.mdscenes/_flow.mdproject-overview.md and scenes/_flow.mdLast updated: YYYY-MM-DD at the top of each sub-doc. This helps identify docs that may need refresh.Last updated fields — no parenthetical annotations.player-controller.md, main-menu.md_flow.md, _config.mdStartup.unity → startup.md