unity-document-system

Generate cited Mermaid diagram documentation for Unity subsystems.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cuozg/oh-my-unity --skill unity-document-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-document-system
Source: https://github.com/cuozg/oh-my-unity/tree/main/skills/unity-document-system
Command: npx skills add https://github.com/cuozg/oh-my-unity --skill unity-document-system

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Documentation gaps in complex Unity subsystems hinder onboarding and maintenance. This skill generates clear, cited documentation that covers architecture, public APIs, and runtime data flows.

Core Features & Use Cases

  • Generates architecture diagrams (Mermaid) and data-flow visuals to illustrate system structure.
  • Produces a public API overview and a dependencies map to support reviews and handoffs.
  • Use Case: onboarding a new engineer to a non-trivial subsystem or preparing architecture reviews after refactors.

Quick Start

Provide the SystemName and trigger keywords to generate its documented architecture, APIs, and data flows.

Frequently Asked Questions about unity-document-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate architecture diagrams for Unity subsystems?

Generate Mermaid diagrams for Unity subsystems by providing the SystemName and trigger keywords; the system outputs data-flow maps and architecture visuals with cited file:line references.

What is the best way to document Unity architecture for engineer onboarding?

Document Unity architecture for onboarding by generating clear, cited documentation covering public APIs and runtime data flows, ensuring new engineers understand subsystem dependencies and structure.

How does cited documentation work for Unity system handoffs?

Cited documentation for Unity system handoffs works by validating every architectural claim and API description with file:line references, ensuring traceability during architecture reviews and refactoring.

Do I need a template to generate Unity subsystem documentation?

You need a system/doc template, Mermaid diagrams, and a template reference file to generate Unity subsystem documentation, ensuring the output structure aligns with your architecture review requirements.

Can I map dependencies for a non-trivial Unity subsystem?

You can map dependencies for non-trivial Unity subsystems by triggering the system-level analysis, which produces a dependencies map and runtime data-flow visuals to support maintenance and handoffs.