Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
Installs into .claude/skills of the current project.
Are you the author of References?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/furkantokkan-references-93a813b4)
---
name: asset-audit
description: "Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations."
argument-hint: "[category|all]"
user-invocable: true
allowed-tools: Read Glob Grep
model: opus
effort: high
# Read-only diagnostic skill — no specialist agent delegation needed
---
## Phase 1: Read Standards
Read the art bible or asset standards from the relevant design docs and the CLAUDE.md naming conventions.
---
## Phase 2: Scan Asset Directories
Discover the project-owned asset roots under `Assets/` first, then scan the
relevant target with Glob. Prefer these canonical locations when present:
- `Assets/Game/Art/**/*` for art assets
- `Assets/Game/Audio/**/*` for audio assets
- `Assets/Game/VFX/**/*` for VFX assets
- `Assets/Game/Shaders/**/*` for shaders
- `Assets/Game/Data/**/*` for data assets and ScriptableObjects
Do not assume third-party content under `Assets/Plugins/`, `Assets/ThirdParty/`,
or package content under `Packages/` is owned by the story. Report it separately
unless the task explicitly includes that dependency.
---
## Phase 3: Run Compliance Checks
**Naming conventions:**
- Art: `[category]_[name]_[variant]_[size].[ext]`
- Audio: `[category]_[context]_[name]_[variant].[ext]`
- All files must be lowercase with underscores
**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
**Orphaned assets:** Search code for references to each asset file. Flag any with no references.
**Missing assets:** Search code for asset references and verify the files exist.
---
## Phase 4: Output Audit Report
```markdown
# 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]
## Verdict: [COMPLIANT / WARNINGS / NON-COMPLIANT]
```
This skill is read-only — it produces a report but does not write files.
---
## Phase 5: Next Steps
- Fix naming violations using the patterns defined in CLAUDE.md.
- Delete confirmed orphaned assets after manual review.
- Run `/content-audit` to cross-check asset counts against GDD-specified requirements.