unity-project-scout

Inspect Unity project version, packages, asmdef layout, and folder structure.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Rayzerrek/dotfiles --skill unity-project-scout-rayzerrek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-project-scout
Source: https://github.com/Rayzerrek/dotfiles/tree/main/.pi/agent/skills/unity-skills/skills/project-scout
Command: npx skills add https://github.com/Rayzerrek/dotfiles --skill unity-project-scout-rayzerrek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely understand an unfamiliar Unity project before proposing changes, so you can avoid conflicting with existing versions, packages, folder conventions, or code architecture.

Core Features & Use Cases

  • Project Reconnaissance: Checks the Unity version, render pipeline, installed packages, and assembly definition layout.
  • Structure Review: Summarizes the Assets folder organization and highlights notable code patterns such as ScriptableObject usage, singletons, event-driven flows, custom inspectors, and tests.
  • Change-Safety Guidance: Identifies conventions, risks, and unknowns so you can make informed recommendations without assuming a clean-slate redesign.
  • Use Case: Before adding a new system to an existing game, use this Skill to confirm the current stack and preserve the project’s established structure.

Quick Start

Ask me to inspect the Unity project and summarize its version, packages, asmdef layout, folder structure, and coding patterns before suggesting any changes.

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 an unfamiliar Unity project before making architecture changes?

A Unity project audit reviews project settings, Packages/manifest.json, Assets, and asmdef files to map the Unity version, render pipeline, dependencies, and coding conventions before proposing any architectural modifications.

What is the best way to map assembly definition layout and folder structure in Unity?

Mapping assembly definition layout involves inspecting asmdef files to understand code separation, while folder structure review summarizes the Assets directory organization to highlight existing conventions and notable code patterns like ScriptableObject usage or singletons.

How do I check Unity version and installed packages before adding a new system to an existing game?

Checking the Unity version and installed packages requires inspecting the project settings and Packages/manifest.json file, establishing the technical baseline to ensure new systems do not conflict with existing dependencies or render pipelines.

When do I need to review coding patterns in a Unity repository?

You need to review coding patterns in a Unity repository when considering architecture or dependency changes, allowing you to identify ScriptableObject usage, singletons, event-driven flows, custom inspectors, and tests to preserve established conventions.

Can I identify render pipeline and dependencies in Unity without assuming a clean-slate redesign?

Yes, you can identify the render pipeline and dependencies by inspecting project settings and manifest files, establishing a technical baseline that highlights conventions, risks, and unknowns for informed recommendations without assuming a clean-slate redesign.

What are the limitations of a Unity project reconnaissance for architecture changes?

Unity project reconnaissance identifies the technical baseline and existing conventions but does not execute changes; it provides change-safety guidance by highlighting risks and unknowns, meaning developers must still manually implement and validate architectural modifications.