mcpField
U
unity-project-scout

unity-project-scout

github.com/besty0728Development1.9k83 installsUpdated today
Repository

About unity-project-scout

unity-project-scout is a project-inspection skill for Unity developers. It records the technical baseline, existing patterns, and constraints before architecture changes are proposed, with an emphasis on preserving consistent conventions and checking dependencies first.

Key features

  1. 01Check Unity version and render pipeline
  2. 02Review packages, asmdef, and folders
  3. 03Identify configuration and architecture patterns
  4. 04Summarize conventions, risks, and unknowns

Use cases

  1. 01Approach an unfamiliar Unity project
  2. 02Prepare for structural changes
  3. 03Audit an existing project setup

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/besty0728/unity-skills --skill unity-project-scout

After installing, type/unity-project-scoutin Claude Code to confirm it loaded.

Details

From the project README

Before calling any skill in this module: if you are about to call a skill with parameters guessed from its name or description, STOP — read this file (or fetch its schema via GET /skills/recommend?includeSchema=true) first. If you already have the parameter definitions from recommend/schema, you may proceed straight to dryRun.

Triggers

  • First approaching an unfamiliar project
  • Before proposing structural changes
  • Auditing existing setup
  • 初次接触陌生项目、在提结构性改动前、盘点现有配置

Unity Project Scout

Use this before recommending architecture changes in an existing project.

Inspect First

Collect only the information needed to avoid clashing with the current project:

  • Unity version and render pipeline
  • Installed packages and notable dependencies
  • asmdef layout, if any
  • Folder structure under Assets/
  • Whether the project already uses:
    • ScriptableObject config
    • service/singleton patterns
    • event-driven flows
    • custom inspectors/property drawers
    • tests
  • Existing naming and code organization style

Suggested Tools / Inputs

  • Unity project info and project settings
  • Script/file search for patterns
  • Local inspection of Packages/manifest.json, Assets/, and *.asmdef

Output Format

  • Technical baseline
  • Existing architectural signals
  • Existing conventions worth preserving
  • Existing risks or inconsistencies
  • Constraints for future suggestions
  • Unknowns that still need confirmation

Guardrails

Mode: Documentation only — no REST skills to gate; load freely under any operating mode (Approval / Auto / Bypass).

  • Do not propose a clean-slate architecture if the project already has a consistent pattern.
  • Do not recommend new dependencies until the current stack is clear.

Comments

Markdown supported