unity-project-scout

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

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/Dylan8865/FinalYearProject --skill unity-project-scout-dylan8865
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unity-project-scout
Source: https://github.com/Dylan8865/FinalYearProject/tree/main/GameDev/Tester/.agents/skills/unity-skills/skills/project-scout
Command: npx skills add https://github.com/Dylan8865/FinalYearProject --skill unity-project-scout-dylan8865

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When joining 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 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 configs, service/singleton patterns, event-driven flows, custom inspectors, asmdef layout, and tests. - Convention & Risk Reporting: Outputs existing conventions worth preserving, risks or inconsistencies, and constraints for future suggestions. - Use Case: A developer opens a client's Unity codebase and asks "看看这个项目". The Skill inspects the manifest, Assets folder, and asmdef files, then reports the project's render pipeline, dependency stack, and coding style before any refactor is proposed. ## Quick Start Ask the assistant to scout this Unity project and report its version, packages, asmdef layout, and existing architecture patterns before suggesting 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 checking the Unity version, render pipeline, and Packages/manifest.json for installed dependencies. Then review the Assets folder structure, asmdef files, and existing patterns like ScriptableObjects or singletons before proposing any modifications.

What should I check first when joining a Unity project?▼

Check the Unity Editor version and render pipeline first, since they constrain everything else. Next inspect the manifest.json for packages, the asmdef layout for assembly boundaries, and the folder organization under Assets to learn the project's conventions.

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

Open Packages/manifest.json in the project root to see all registered package dependencies and versions. You can also review the Package Manager window in the Unity Editor for the same information.

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

Avoid clean-slate proposals when the project already follows a consistent pattern, such as established ScriptableObject configs or event-driven flows. Also avoid recommending 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 project settings, manifest.json, Assets, and asmdef files without changing the project, and it carries no REST or execution gating requirements.