unity-project-scout

Inspect an existing Unity project's architecture, packages, and conventions before proposing changes.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/ethanJPope/Our-Main-Hackathon-Game --skill unity-project-scout-ethanjpope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-project-scout
Source: https://github.com/ethanJPope/Our-Main-Hackathon-Game/tree/main/.agents/skills/unity-skills/skills/project-scout
Command: npx skills add https://github.com/ethanJPope/Our-Main-Hackathon-Game --skill unity-project-scout-ethanjpope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When approaching an unfamiliar Unity project, proposing architecture changes without understanding the existing setup leads to clashing patterns, redundant dependencies, and broken conventions. This Skill guides a structured reconnaissance of the project so recommendations respect what already exists. ## Core Features & Use Cases - Technical Baseline Collection: Gathers Unity version, render pipeline, installed packages, and asmdef layout from Packages/manifest.json and Assets/. - Architecture Signal Detection: Identifies existing use of ScriptableObject config, service/singleton patterns, event-driven flows, custom inspectors, and tests. - Convention & Risk Reporting: Outputs existing conventions worth preserving, risks or inconsistencies, and constraints for future suggestions. - Use Case: Before refactoring a legacy Unity codebase, run this scout to produce a baseline report covering folder structure, naming style, and dependencies, so your proposal aligns with the current stack instead of imposing a clean-slate redesign. ## Quick Start Ask the assistant to scout this Unity project and report its version, render pipeline, packages, asmdef layout, and existing architectural patterns before suggesting any structural 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 existing Unity project before refactoring?

Audit a Unity project by collecting its Unity version, render pipeline, installed packages from Packages/manifest.json, asmdef layout, and Assets/ folder structure. Then identify existing patterns such as ScriptableObject config, singletons, and event-driven flows before proposing changes.

What should I check before proposing Unity architecture changes?

Check the Unity version, render pipeline, package dependencies, asmdef organization, naming conventions, and whether the project already uses service patterns, custom inspectors, or tests. Avoid recommending a clean-slate architecture if a consistent pattern already exists.

How do I find installed packages in a Unity project?

Installed packages are declared in Packages/manifest.json at the project root. Inspecting this file reveals the exact dependencies and versions, which prevents recommending packages that conflict with or duplicate the current stack.

Does this Unity project inspection modify any files?

No, the inspection is documentation-only and read-only. It collects information from project settings, manifest files, and script patterns, then outputs a baseline report without changing project files or adding dependencies.

When should I not recommend new Unity dependencies?

Do not recommend new dependencies until the current stack is fully understood. If the project already solves a problem with an existing package or pattern, adding another dependency creates redundancy and maintenance risk.