asset-audit

## Phase 1: Read Standards Read the art bible or asset standards from the relevant design docs: - `design/art/art-bible.md` — visual and naming standards - `design/gdd/asset-manifest.md` — expected asset list if it exists - `.agents/rules/data-files.md` — data file standards - `AGENTS.md` — project naming conventions If no art bible exists, note: "No art bible found. Auditing against general game industry conventions." and proceed. --- ## Phase 2: Scan Asset Directories Use Glob to index all asset files in the target scope. Scan these directories: ``` Glob pattern="assets/art/**/*.{png,jpg,svg,psd,tres,tscn}" (art) Glob pattern="assets/audio/**/*.{ogg,mp3,wav,flac}" (audio) Glob pattern="assets/vfx/**/*.{tscn,tres,gdshader}" (VFX) Glob pattern="assets/shaders/**/*.{gdshader,tres}" (shaders) Glob pattern="assets/data/**/*.{json,yaml,csv,tres}" (data) ``` If the argument specifies a category (e.g., `art`), limit to that directory. For each file found, use Bash `stat` (or Node.js `fs.statSync` equivalent via Execute) to record file size. --- ## Phase 3: Run Compliance Checks ### 3a: Naming Conventions Check each file against the expected naming pattern: - Art: `[category]_[name]_[variant]_[size].{png,jpg}` (e.g., `char_player_idle_256.png`) - Audio: `[category]_[context]_[name]_[variant].{ogg,mp3}` (e.g., `sfx_combat_sword_hit_01.ogg`) - Shaders: `[type]_[category]_[name].gdshader` (e.g., `spatial_env_water.gdshader`) - All files must use lowercase with underscores,...