unity-project-scout

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

2|Updated May 18, 2026
One-click install
npx skills add https://github.com/pcone-mm/NewFPG --skill unity-project-scout-pcone-mm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-project-scout
Source: https://github.com/pcone-mm/NewFPG/tree/main/.agents/skills/unity-skills/skills/project-scout
Command: npx skills add https://github.com/pcone-mm/NewFPG --skill unity-project-scout-pcone-mm

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 asmdef layout from Packages/manifest.json and Assets/. - Pattern Detection: Identifies existing use of ScriptableObject configs, service/singleton patterns, event-driven flows, custom inspectors, and tests. - Use Case: A developer joins a team maintaining an existing Unity game and asks "看看这个项目". The Skill produces a report covering the technical baseline, existing architectural signals, conventions worth preserving, risks, and constraints for future suggestions. ## Quick Start Ask the assistant to scout this Unity project and report its version, packages, asmdef structure, and existing 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 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 configs, singletons, and event-driven flows before proposing anything.

What should I check in a Unity project before proposing architecture changes?

Check the Unity version, render pipeline, package dependencies, asmdef organization, folder structure under Assets/, naming conventions, and whether tests or custom inspectors exist. This prevents recommending patterns that clash with the current setup.

How do I find which packages a Unity project uses?

Inspect the Packages/manifest.json file 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 a clean-slate architecture in Unity?

Avoid clean-slate proposals when the project already has a consistent pattern, such as established ScriptableObject configs or service patterns. Preserve existing conventions and only suggest changes that align with the current structure.

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 without altering the project, and it works under any operating mode.