unity-project-scout

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

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications --skill unity-project-scout-du-qwq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-project-scout
Source: https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications/tree/main/.agents/skills/unity-skills/skills/project-scout
Command: npx skills add https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications --skill unity-project-scout-du-qwq

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 from Packages/manifest.json, and asmdef layout. - Pattern Detection: Identifies existing use of ScriptableObject configs, service/singleton patterns, event-driven flows, custom inspectors, and tests. - Structured Audit Output: Produces a report covering existing conventions, risks, constraints, and open questions. - Use Case: A developer joins a team mid-project and asks "看看这个项目". The Skill inspects the folder structure under Assets/, the manifest, and asmdef files, then reports the project's architecture signals so any future suggestions respect existing conventions. ## Quick Start Ask the assistant to scout this Unity project and summarize its version, packages, asmdef 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 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 flows before proposing any changes.

What should I check in a Unity project before refactoring?

Check the Unity version, package dependencies, asmdef boundaries, folder organization, naming conventions, and whether the project already uses tests or custom inspectors. This prevents recommending a clean-slate architecture that clashes with consistent existing patterns.

How do I find which packages a Unity project uses?

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

Does this Unity project audit modify any project files?

No, the audit is documentation-only and read-only. It inspects project settings, manifest files, and code patterns, then outputs a report of baselines, conventions, risks, and open questions without changing anything.

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

Avoid proposing a clean-slate architecture when the project already has a consistent, working pattern. Also avoid recommending new dependencies until the current package stack and asmdef boundaries are fully understood.