unity-project-scout

Inspect Unity projects to produce a technical baseline of version, render pipeline, packages, asmdef layout, and folder structure.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/Yuan-Zzzz/FrogRE --skill unity-project-scout-yuan-zzzz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-project-scout
Source: https://github.com/Yuan-Zzzz/FrogRE/tree/main/.codex/skills/unity-skills/skills/project-scout
Command: npx skills add https://github.com/Yuan-Zzzz/FrogRE --skill unity-project-scout-yuan-zzzz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineers and architects gather a concise, non-invasive technical baseline of an existing Unity project so recommendations do not conflict with established structure, dependencies, or conventions.

Core Features & Use Cases

  • Inspect Unity editor version, render pipeline, and notable package dependencies from Packages/manifest.json.
  • Enumerate asmdef layout, Assets/ folder structure, and detectable coding/organization patterns such as ScriptableObject usage, singletons/services, custom editors, and tests.
  • Use Case: Before proposing an engine upgrade or architecture refactor, run this scout to preserve existing conventions, identify risks, and list constraints for safe changes.

Quick Start

Ask the assistant to "inspect the project and produce a technical baseline listing Unity version, render pipeline, installed packages, asmdef layout, folder structure, coding patterns, conventions to preserve, risks, constraints, and outstanding unknowns."

Frequently Asked Questions about unity-project-scout

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

FAQPage Schema
How do I audit a Unity project's architecture before proposing a refactor?

To profile a Unity project, you must inspect the Packages/manifest.json, Assets/ folder structure, and *.asmdef files. This reveals the render pipeline, package dependencies, and assembly definitions, providing a concise technical baseline for safe integration planning.

Can I inspect Unity package dependencies and asmdef layout non-invasively?

You can non-invasively inspect Unity package dependencies and asmdef layout by analyzing local manifest files and assembly definitions. This produces a concise technical baseline listing installed packages, folder structure, and coding patterns without modifying the existing codebase.

What do I need to analyze before upgrading a Unity engine version?

Before a Unity engine upgrade, you need local access to Packages/manifest.json and *.asmdef files to analyze package dependencies and assembly definitions. This identifies version constraints, render pipeline settings, and architectural risks to ensure a safe upgrade.

Does profiling a Unity codebase detect ScriptableObject usage and singletons?

Yes, profiling a Unity codebase detects ScriptableObject usage, singletons, and custom editors by inspecting the Assets/ folder structure and asmdef layout. This reconnaissance identifies established coding patterns and architectural signals for integration planning.

What are the limitations when inspecting Unity folder structure for code-review reconnaissance?

Inspecting Unity folder structure requires local access to Packages/manifest.json, Assets/, and *.asmdef files. A key limitation is that while it identifies detectable coding patterns, it also lists remaining unknowns and constraints that require further investigation before architecture changes.