asset-audit

To audit app assets, this skill validates naming conventions, size budgets, and format compliance across project assets. It reads standards from .claude/docs/technical-preferences.md and assets/asset-standards.md to ensure all images meet requirements.

You find missing references and orphaned assets by running a reference audit across code and configuration files. The skill cross-references assets located in the assets/ directory against code usage to identify orphans and missing links.

Asset reference integrity ensures every asset in your project is properly linked and utilized, preventing brittle builds. Missing references cause runtime crashes, while orphaned assets waste app size budgets and create unnecessary rework.

Yes, the asset audit works with iOS and Android store assets. It validates density requirements and identifies missing platform-specific assets, making it suitable for projects preparing store-pack submissions with screenshots and icons.

You generate a remediation plan by running the audit, which produces an actionable report for design and engineering teams. This report details format compliance failures and oversized images, guiding the next sprint's fixes.

A limitation of automating asset validation is that it relies on predefined standards in technical-preferences.md and asset-standards.md. Without these configuration files explicitly defining naming and size budgets, the audit cannot enforce project-specific compliance rules.