Unity Project Polished

Comprehensive Unity game development statusline showing project structure health, asset counts, platform targets, and development environment status.

When to Use This Setting

Apply this setting when you need to:

• Monitor Unity project health indicators including asset counts, scene totals, and folder structure compliance
• Track multi-platform build readiness for iOS, Android, PC, and WebGL targets from your statusline
• Verify your Unity development environment setup including version, packages, and Git LFS configuration Consider alternatives when:
• Your project is not a Unity game and the Unity-specific directory checks would always return generic results
• You use Unity's built-in console and profiler panels and do not need redundant statusline-level project info

Quick Start

Configuration

Copy
name: unity-project-polished
type: setting
category: statusline

Example Application

Copy
claude setting:apply unity-project-polished

Example Output

Setting applied. Changes:
- statusLine.type: command
- statusLine.command: bash unity-project-status inline
- detection: Assets + ProjectSettings directories
- asset_tracking: scripts, textures, prefabs, scenes
- platform_checks: iOS, Android, PC, WebGL
- environment: Unity version, packages, Git LFS

Core Concepts

Unity Project Overview

Aspect	Details
Project Detection	Confirms Unity project by checking for Assets and ProjectSettings directories
Asset Counting	Tallies scripts (.cs), textures (.png/.jpg), prefabs (.prefab), and scenes (.unity)
Folder Structure	Validates recommended _Project structure with Scripts, Art, Audio, Prefabs, Scenes
Platform Status	Checks build output directories for each configured target platform
Version Tracking	Reads Unity version from ProjectSettings/ProjectVersion.txt when available

Unity Project Architecture

+--------------------+     +---------------------+     +-------------------+
| Project Validator  |---->| Asset Counter       |---->| Platform Checker  |
| Assets/ exists?    |     | find *.cs *.png     |     | Builds/iOS? etc   |
| ProjectSettings/?  |     | *.prefab *.unity    |     | per target dir    |
+--------------------+     +---------------------+     +-------------------+
         |                          |                          |
         v                          v                          v
  +----------------+      +-------------------+      +------------------+
  | Version Reader |      | Structure Audit   |      | Status Assembler |
  | ProjectVersion |      | _Project layout   |      | version+assets+  |
  | .txt parser    |      | compliance check  |      | platforms+health |
  +----------------+      +-------------------+      +------------------+

Configuration

Parameter	Type	Default	Description
project_root	string	"."	Root directory of the Unity project relative to working directory
track_scripts	boolean	true	Count C# script files in the asset summary
track_textures	boolean	true	Count texture files (png, jpg, tga) in the asset summary
platform_targets	string[]	["iOS","Android","PC","WebGL"]	List of build platform directories to check
structure_validation	boolean	true	Enable recommended folder structure compliance checking

Best Practices

1. Establish folder structure conventions early - The structure validation checks for the recommended _Project layout. Set up this structure at project inception so the statusline shows green compliance from day one rather than accumulating technical debt.
2. Monitor asset counts for scope creep - Watch the texture and prefab counts grow over time. If counts spike unexpectedly, investigate whether unoptimized or duplicate assets are being added that could impact build size and loading performance.
3. Use platform checks for CI gating - Integrate the platform checker logic into your CI pipeline so builds are automatically verified for all target platforms. The statusline gives you the same visibility locally during development.
4. Configure Git LFS for large assets - Unity projects contain large binary files. Ensure your .gitattributes file tracks *.png, *.fbx, *.wav, and other binary formats with Git LFS to prevent repository bloat that the asset counter would otherwise highlight.
5. Update platform targets per milestone - Early in development you may only target PC. Update the platform_targets list as you add mobile or console builds so the statusline reflects your current release roadmap.

Common Issues

1. Project not detected despite being a Unity project - The validator requires both Assets and ProjectSettings directories at the project root. If you launched Claude Code from a subdirectory, navigate to the project root or adjust project_root to point to the correct location.
2. Asset counts seem too high - The find command counts all matching files including those in Plugins, third-party packages, and Unity auto-generated files. Add exclusion patterns for Library, Temp, and Packages directories to count only your project assets.
3. Platform build status all show pending - You have not run any builds yet. Build your project for at least one target platform to create the output directory that the checker looks for.