asset-audit

To check game assets for naming convention violations and missing references, scan your asset directories using deterministic Glob and Grep patterns against lowercase/underscore rules defined in your CLAUDE.md. This generates an audit report identifying orphaned assets and missing code references.

Game asset compliance auditing is the process of validating art, audio, VFX, shader, and data files against studio standards before production builds. You need it when file size budgets, format mismatches, or orphaned assets risk breaking your build readiness or game design document expectations.

Yes, you can audit multiple asset folders simultaneously. The audit performs deterministic directory scanning across assets/art, assets/audio, assets/vfx, assets/shaders, and assets/data to check per-type budgets, file formats, and naming patterns in one compliance report.

To find orphaned assets with no code references, run a directory scan that reconciles game production files against code and game design document expectations. The resulting audit report flags any art, audio, VFX, or shader assets lacking valid code references.

The best way to validate file size budgets and formats for game production is to run an automated audit that reads your studio standards and checks per-type file constraints. It identifies size mismatches and format violations across all asset categories before build time.

Asset auditing requires no specific dependencies or components to run. It relies on deterministic Glob and Grep scanning to evaluate your game asset directories, reading your existing CLAUDE.md naming conventions and studio standards to produce the compliance report.