unity-screen-doc

Generate planner-focused Markdown documentation for Unity game screens.

Updated Aug 23, 2026

Search Tags:#unity #documentation #game-design #screen-doc #screen-spec #UI-flow #planner

Ready to run

npx skills add https://github.com/Wonderplanet/glow-brain --skill unity-screen-doc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unity-screen-doc
Source: https://github.com/Wonderplanet/glow-brain/tree/main/.claude/skills/unity-screen-doc
Command: npx skills add https://github.com/Wonderplanet/glow-brain --skill unity-screen-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill translates Unity screen implementations into planner-focused, non-technical documentation that describes player experience, screen flow, and data interactions, reducing the time needed to communicate UI design and ensuring the team shares a common understanding of how screens influence gameplay.

Core Features & Use Cases

Automated screen documentation: Generates Markdown docs detailing the behavior, user interactions, and screen flow without exposing implementation details.
Player-centric focus: Emphasizes how UI elements, transitions, and scenes impact gameplay pacing and player decisions.
Master data guidance support: Explains how master data settings shape screen mechanics and constraints to inform design decisions.

Quick Start

Provide the Unity screen name (for example, InventoryScreen) and run the skill to generate the planner-focused documentation for that screen.

Frequently Asked Questions about unity-screen-doc

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

FAQPage Schema

How do I convert Unity screen code into documentation for game planners?▼

This Skill generates planner-focused Markdown documentation from Unity screen implementations, translating code into non-technical descriptions of player experience, UI interactions, screen flow, and how master data constraints shape gameplay without exposing implementation details.

Can I use this to document multiple screens in a Unity game?▼

Yes, the Skill applies across multiple screens in Unity-based game clients. Provide each screen name (for example, InventoryScreen or ShopScreen) to generate documentation for that specific screen's player-facing behavior and interactions.

What information does the documentation include about screen mechanics?▼

Documentation details player interactions, navigation flows, UI element behavior, screen transitions, and how master data settings constrain or enable gameplay mechanics—all written in terminology planners use rather than developer language.

Do I need to know how to code to use this Skill?▼

No, the Skill is designed for planners and non-technical team members. You only need to provide the Unity screen name; the output is automatically formatted in planner-friendly Markdown without code or file path references.

How does this help align team understanding of screen design?▼

By translating implementation details into a shared, non-technical format, the Skill reduces miscommunication about UI design, player flow, and data interactions—ensuring designers, planners, and developers discuss screens using the same vocabulary.