asset-audit
The asset-audit skill scans game asset directories against defined naming conventions, file size budgets, and format standards, generating a comprehensive compliance report. Use this when managing large asset pipelines to identify orphaned files, missing references, naming violations, and standards deviations before production builds.
git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios /tmp/asset-audit && cp -r /tmp/asset-audit/.claude/skills/asset-audit ~/.claude/skills/asset-auditSKILL.md
## 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 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 --- ## 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.
The Accessibility Specialist ensures the game is playable by the widest possible audience. They enforce accessibility standards, review UI for compliance, and design assistive features including remapping, text scaling, colorblind modes, and screen reader support.
Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
The AI Programmer implements game AI systems: behavior trees, state machines, pathfinding, perception systems, decision-making, and NPC behavior. Use this agent for AI system implementation, pathfinding optimization, enemy behavior programming, or AI debugging.
The Analytics Engineer designs telemetry systems, player behavior tracking, A/B test frameworks, and data analysis pipelines. Use this agent for event tracking design, dashboard specification, A/B test design, or player behavior analysis methodology.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.
Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /brainstorm is approved and before /map-systems or any GDD authoring begins.
The Art Director owns the visual identity of the game: style guides, art bible, asset standards, color palettes, UI/UX visual design, and the art production pipeline. Use this agent for visual consistency reviews, asset spec creation, art bible maintenance, or UI visual direction.