unity-project-scout

Inspects Unity project version, packages, asmdef layout, and coding patterns before proposing changes.

Updated Oct 13, 2025
One-click install
npx skills add https://github.com/Darth-Carrotpie/ProxyCore --skill unity-project-scout-darth-carrotpie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unity-project-scout
Source: https://github.com/Darth-Carrotpie/ProxyCore/tree/main/.agents/skills/unity-skills/skills/project-scout
Command: npx skills add https://github.com/Darth-Carrotpie/ProxyCore --skill unity-project-scout-darth-carrotpie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When approaching an unfamiliar Unity project, proposing architectural changes without understanding the existing setup leads to clashing patterns, redundant dependencies, and broken conventions. This Skill guides a structured reconnaissance of the project before any recommendations are made. ## Core Features & Use Cases - Technical Baseline Collection: Gathers Unity version, render pipeline, installed packages, and Packages/manifest.json contents. - Architecture Signal Detection: Identifies existing use of ScriptableObject config, service/singleton patterns, event-driven flows, custom inspectors, and tests. - Convention & Risk Reporting: Outputs existing naming conventions, folder structure under Assets/, asmdef layout, risks, and constraints for future suggestions. - Use Case: A developer joins an existing Unity codebase and asks the agent to review the project. The Skill ensures the agent first inspects the manifest, asmdefs, and folder structure, then reports the baseline before suggesting any structural changes. ## Quick Start Ask the agent to scout this Unity project and report its version, packages, asmdef layout, and existing architectural 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 changes?▼

Start by collecting the Unity version, render pipeline, installed packages from Packages/manifest.json, asmdef layout, and Assets/ folder structure. Then identify existing patterns like ScriptableObject config, singletons, and event-driven flows before proposing any changes.

What should I check in a Unity project before refactoring?▼

Check the Unity version, package dependencies, asmdef organization, folder conventions, and whether the project already uses consistent patterns such as service locators or event systems. Avoid proposing a clean-slate architecture if a consistent pattern already exists.

How do I find which packages a Unity project uses?▼

Inspect Packages/manifest.json at the project root, which lists all installed package dependencies and versions. This reveals the current stack so you avoid recommending redundant or conflicting dependencies.

When should I not recommend new architecture for a Unity project?▼

Avoid recommending new architecture when the project already follows a consistent pattern, such as established ScriptableObject config or event-driven flows. Also hold off on new dependencies until the current package stack is fully understood.

Does this Unity project inspection modify any files?▼

No, the inspection is documentation-only and read-focused. It collects information from the manifest, asmdefs, and folder structure, then outputs a baseline report without changing project files.