Files
Claude-Code-Game-Studios/.claude/skills/asset-audit/SKILL.md
Donchitos 392e3befec Adopt new Claude Code features: agent memory, context fork, worktree isolation, SubagentStop hook
- Add `memory: project` to 14 specialist agents for cross-session learning
- Add `context: fork` + `agent:` to 6 analysis skills to preserve main context
- Add `isolation: worktree` to prototyper agent for safe throwaway experiments
- Add SubagentStop hook to complete agent audit trail (start + stop logging)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-09 13:58:05 +11:00

2.3 KiB

name, description, argument-hint, user-invocable, allowed-tools, context, agent
name description argument-hint user-invocable allowed-tools context agent
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 fork Explore

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]