Asset Audit

Asset Audit

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

Category: development Source: Donchitos/Claude-Code-Game-Studios

Asset Audit

What Is This

The "Asset Audit" skill is a diagnostic tool designed for game development projects, focusing on enforcing and verifying asset pipeline standards. It systematically audits a project’s game assets for compliance with established naming conventions, file format and size requirements, and reference integrity. This tool reads the relevant asset standards and naming conventions-especially those outlined in the CLAUDE.md documentation and the project's art bible-and applies them to all assets located in predefined directories. It identifies orphaned files (assets present on disk but unused in code), missing assets (referenced in code but not present on disk), and any violations of format or naming rules. The skill can be invoked on demand, operates in a read-only diagnostic mode, and does not delegate tasks to specialist agents.

Why Use It

Asset consistency is essential for large and small game projects alike. Disorganized or non-standardized assets can cause build failures, runtime errors, bloated distributions, and costly refactoring late in development. Manual asset reviews are time-consuming and error-prone, especially as project scale increases. The Asset Audit skill automates this process, providing rapid feedback to developers and artists. By enforcing uniform conventions, it helps teams:

  • Reduce errors caused by inconsistent asset names or formats.
  • Ensure that all assets referenced in code are present and valid.
  • Prevent distribution of unused (orphaned) files, reducing final build size.
  • Catch violations of file size, dimension, or encoding standards early.
  • Maintain compliance with the project’s technical art direction.

How to Use It

1. Read Standards

The audit process begins by reading and interpreting the project's asset standards. This includes:

  • The art bible or asset standards defined in design documentation.
  • Naming conventions and file requirements specified in CLAUDE.md.

This ensures the audit runs against the most current and project-specific rules.

2. Scan Asset Directories

The skill scans the following directories using globbing patterns to collect all relevant files:

  • assets/art/**/* for art assets (textures, sprites, models)
  • assets/audio/**/* for audio assets (SFX, music)
  • assets/vfx/**/* for visual effects
  • assets/shaders/**/* for shader code
  • assets/data/**/* for data files (JSON, YAML, etc.)

This scan builds an inventory of assets by category for later checks.

3. Run Compliance Checks

The core of the tool is its suite of compliance checks:

Naming Conventions:
Every file is checked against strict naming rules, such as:

  • Art: [category]_[name]_[variant]_[size].[ext]
  • Audio: [category]_[context]_[name]_[variant].[ext]
  • All filenames must be lowercase and use underscores as separators.

File Standards:
Files are validated for technical requirements:

  • Textures: Must have power-of-two dimensions, correct formats (e.g., PNG for UI), and not exceed size budgets.
  • Audio: Must match sample rate and format (OGG for SFX, OGG/MP3 for music), and be within duration limits.
  • Data: Must be valid JSON or YAML and conform to project schema.

Orphaned Assets:
The skill searches the codebase for references to each asset file using tools like grep. Any file that is not referenced in code is flagged as orphaned.

Missing Assets:
The codebase is also scanned for asset references. If a referenced asset is missing from disk, it is flagged as a missing asset.

4. Output Audit Report

After all checks, the skill produces an audit report detailing:

  • Naming convention violations (with file paths and expected format).
  • File standard violations (e.g., wrong format, size over budget).
  • Orphaned files (assets not used anywhere in code).
  • Missing assets (referenced but not present).
  • Summary and suggested actions.

Example Report Fragment:

### Naming Violations:
- assets/art/character/Hero01.png  
  *Expected*: character_hero_01_512x512.png

### File Format Violations:
- assets/audio/music/level_theme.mp3  
  *Expected*: OGG format, found MP3

### Orphaned Assets:
- assets/vfx/unused_effect.vfx

### Missing Assets:
- Referenced in code: assets/art/ui/button_press_128x128.png  
  *File not found*

When to Use It

Invoke the Asset Audit skill:

  • Before major project milestones or build submissions.
  • When onboarding new team members to verify asset contributions.
  • After large asset imports or refactors.
  • As part of automated CI/CD pipelines to catch regressions early.
  • Whenever asset standards are updated to ensure compliance across the project.

Important Notes

  • This skill is read-only and does not modify assets or code.
  • It requires up-to-date standards documentation (design docs, CLAUDE.md) for accurate results.
  • Compliance checks are only as strict as the rules provided in standards files.
  • The tool uses file globbing and code search utilities (Read, Glob, Grep), so ensure directory structures and code references are compatible.
  • False positives may occur if assets are referenced dynamically or via external systems not captured by static code analysis.
  • Regular use helps maintain a clean, efficient, and reliable asset pipeline, reducing technical debt and streamlining production.