unity-project-scout

Inspects an existing Unity project's architecture, packages, and conventions before recommending changes.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill unity-project-scout-pikachu0310
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-project-scout
Source: https://github.com/pikachu0310/codex-agent-ops-public/tree/main/.agents/skills/unity-skills/skills/project-scout
Command: npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill unity-project-scout-pikachu0310

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 so recommendations respect what is already there. ## 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 asmdef layouts, ScriptableObject config, service/singleton patterns, event-driven flows, custom inspectors, and tests. - Convention Preservation: Surfaces naming styles, folder organization under Assets/, and risks or inconsistencies before any structural proposal. - Use Case: Before refactoring a legacy Unity project, run this scout to produce a report of existing patterns and constraints, ensuring your suggestions build on the current architecture instead of replacing it blindly. ## 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 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 any changes.

What should I check before proposing Unity architecture changes?

Check the project's render pipeline, package dependencies, assembly definition layout, naming conventions, and whether it already uses service patterns, custom inspectors, or tests. Recommendations should preserve consistent existing patterns rather than impose a clean-slate architecture.

Does this Unity project scout modify any project files?

No, the scout is documentation-only and performs read-only inspection of project settings, manifest files, and folder structure. It produces a report of baselines, signals, and risks without editing the project.

When should I not recommend new Unity dependencies?

Avoid recommending new dependencies until the current package stack in Packages/manifest.json is fully understood. Adding packages before mapping existing ones risks duplication, version conflicts, and clashing architectural patterns.

How do I find asmdef usage in a Unity project?

Search the project for *.asmdef files and review how assemblies are partitioned across the Assets folder. The asmdef layout reveals module boundaries and compilation organization that should inform any structural proposal.