cocos-asset-review-director

Cocos Asset Review Director

Overview

Use this skill to prevent generated assets from silently becoming gameplay defects. It reviews whether assets are usable for the specific game, not just whether the files exist or look attractive.

This skill coordinates with cocos-art-direction-director and cocos-asset-pipeline-director. Art direction defines the visual promise, asset pipeline generates and imports files, and this skill accepts, rejects, or requests targeted regeneration before implementation relies on them.

Review Philosophy

Review with guided judgment, not a rigid checklist. The skill should help Codex ask the right production questions while preserving room for creative choices, genre variation, stylization, and deliberate exceptions.

Use hard gates only for defects that clearly break the asset's job: corrupt files, wrong role, unusable transparency, unreadable gameplay-critical silhouettes, missing required frames, misleading feedback, broken import metadata, or runtime/package risks. Treat most other findings as contextual tradeoffs: accept, adapt, regenerate, or defer based on the current slice and design intent.

Core Workflow

1. Recover the asset contract.
   • Identify the game genre, camera, design resolution, target runtime size, asset role, gameplay meaning, interaction context, style target, and whether the asset is static, animated, VFX, UI, background, or audio.
   • If the asset contract is missing, write the smallest contract needed to review it instead of accepting the asset by taste.
2. Inspect the actual artifact.
   • Prefer visual inspection for PNG, sprite sheets, UI packs, and contact sheets.
   • Check metadata, dimensions, frame layout, file names, transparency, and project placement when available.
   • For batched contact sheets, review the source sheet and the sliced cells. Check for merged cells, accidental multi-subject clutter, cell drift, bad crops, duplicate cells, unusable cells, and whether the batch actually reduced generation calls.
3. Judge design fit.
   • Verify the asset communicates the intended gameplay identity: player, enemy, hazard, reward, neutral prop, background, UI, or feedback effect.
   • Check whether shape, color, value, motion, scale, material, faction language, and feedback meaning match the design and art direction.
4. Judge runtime fitness.
   • Check mobile readability, alpha cleanliness, padding, atlas friendliness, collision fit, frame consistency, audio length, import metadata, and package-size risk.
5. Decide and hand off.
   • Mark each asset as accepted, accepted-with-notes, needs-adaptation, needs-regeneration, or rejected.
   • Regenerate or adapt only the smallest failed unit when possible.