Files
Claude-Code-Game-Studios/.claude/skills/asset-audit/SKILL.md
Donchitos ad540fe75d Game Studio Agent Architecture — complete setup (Phases 1-7)
48 coordinated Claude Code subagents for indie game development:
- 3 leadership agents (creative-director, technical-director, producer)
- 10 department leads (game-designer, lead-programmer, art-director, etc.)
- 23 specialist agents (gameplay, engine, AI, networking, UI, tools, etc.)
- 12 engine-specific agents (Godot, Unity, Unreal with sub-specialists)

Infrastructure:
- 34 skills (slash commands) for workflows, reviews, and team orchestration
- 8 hooks for commit validation, asset checks, session management
- 11 path-scoped rules enforcing domain-specific standards
- 28 templates for design docs, reports, and collaborative protocols

Key features:
- User-driven collaboration protocol (Question → Options → Decision → Draft → Approval)
- Engine version awareness with knowledge-gap detection (Godot 4.6 pinned)
- Phase gate system for development milestone validation
- CLAUDE.md kept under 80 lines with extracted doc imports

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-13 21:04:24 +11:00

2.3 KiB

name, description, argument-hint, user-invocable, allowed-tools
name description argument-hint user-invocable allowed-tools
asset-audit Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations. [category|all] true Read, Glob, Grep

When this skill is invoked:

  1. Read the art bible or asset standards from the relevant design docs and the CLAUDE.md naming conventions.

  2. Scan the target asset directory using Glob:

    • assets/art/**/* for art assets
    • assets/audio/**/* for audio assets
    • assets/vfx/**/* for VFX assets
    • assets/shaders/**/* for shaders
    • assets/data/**/* for data files
  3. Check naming conventions:

    • Art: [category]_[name]_[variant]_[size].[ext]
    • Audio: [category]_[context]_[name]_[variant].[ext]
    • All files must be lowercase with underscores
  4. Check file standards:

    • Textures: Power-of-two dimensions, correct format (PNG for UI, compressed for 3D), within size budget
    • Audio: Correct sample rate, format (OGG for SFX, OGG/MP3 for music), within duration limits
    • Data: Valid JSON/YAML, schema-compliant
  5. Check for orphaned assets by searching code for references to each asset file.

  6. Check for missing assets by searching code for asset references and verifying the files exist.

  7. Output the audit:

# Asset Audit Report -- [Category] -- [Date]

## Summary
- **Total assets scanned**: [N]
- **Naming violations**: [N]
- **Size violations**: [N]
- **Format violations**: [N]
- **Orphaned assets**: [N]
- **Missing assets**: [N]
- **Overall health**: [CLEAN / MINOR ISSUES / NEEDS ATTENTION]

## Naming Violations
| File | Expected Pattern | Issue |
|------|-----------------|-------|

## Size Violations
| File | Budget | Actual | Overage |
|------|--------|--------|---------|

## Format Violations
| File | Expected Format | Actual Format |
|------|----------------|---------------|

## Orphaned Assets (no code references found)
| File | Last Modified | Size | Recommendation |
|------|-------------|------|---------------|

## Missing Assets (referenced but not found)
| Reference Location | Expected Path |
|-------------------|---------------|

## Recommendations
[Prioritized list of fixes]