unity-project-scout

Analyze Unity projects to produce a technical and architectural baseline.

8|1|Updated Oct 7, 2025
One-click install
npx skills add https://github.com/Zzulin/unity-project01 --skill unity-project-scout-zzulin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-project-scout
Source: https://github.com/Zzulin/unity-project01/tree/main/URP1/Plugins/Unity-Skills-main/SkillsForUnity/unity-skills~/skills/project-scout
Command: npx skills add https://github.com/Zzulin/unity-project01 --skill unity-project-scout-zzulin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineers and architects quickly establish a reliable technical baseline for an existing Unity project so recommendations do not conflict with the current codebase or conventions.

Core Features & Use Cases

  • Dependency and Version Discovery: Detect Unity editor version, active render pipeline, and installed packages by inspecting project settings and Packages/manifest.json.
  • Codebase Organization Mapping: Enumerate asmdef layouts, Assets/ folder structure, and notable folders to reveal module boundaries and compilation contexts.
  • Architectural Signals: Identify use of ScriptableObject configuration, service/singleton patterns, event-driven flows, custom inspectors/property drawers, and presence of tests to preserve existing patterns.
  • Risk & Constraint Reporting: Surface inconsistencies, missing tests, risky dependencies, and constraints to inform safe evolution of architecture.
  • Use Case: Run before proposing refactors or new dependencies to ensure compatibility with existing assembly definitions and project conventions.

Quick Start

Inspect the current Unity project and produce a technical baseline listing Unity version, render pipeline, packages, asmdef layout, Assets folder structure, and detected architectural patterns.

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 before making architecture changes?

You can audit a Unity project by inspecting Packages/manifest.json, Assets/ folders, and *.asmdef layouts to produce a technical baseline identifying the Unity version, render pipeline, installed packages, and module boundaries.

What architectural patterns can be detected in a Unity codebase?

Architectural pattern detection in a Unity codebase flags ScriptableObject configuration, service/singleton patterns, event-driven flows, custom inspectors, and property drawers to reveal existing coding conventions.

How do I map asmdef layouts and Assets organization in Unity?

To map asmdef layouts and Assets organization, enumerate assembly definitions and folder structures to reveal module boundaries and compilation contexts for safe architectural evolution.

Does this Unity project audit detect the active render pipeline and dependencies?

Yes, the Unity project audit detects the active render pipeline and lists installed package dependencies by inspecting project settings and Packages/manifest.json to inform safe refactoring.

What are the limitations of running a Unity architecture audit before refactoring?

Running a Unity architecture audit surfaces inconsistencies, missing tests, and risky dependencies as constraints, but it does not modify the codebase; it only establishes a baseline to inform safe evolution.