cocos-asset-pipeline-director

Cocos Asset Pipeline Director

Overview

Use this skill to direct Cocos Creator asset work through a dedicated asset-generation MCP instead of treating generated art as loose files. The skill chooses the right asset pipeline, constrains prompts for game-runtime use, preserves generated metadata, and verifies that outputs are ready to import or wire into a Cocos project.

The skill is intentionally a pipeline layer, not a competing image model wrapper. If the configured MCP can produce or adapt the requested asset, use it first.

Use cocos-asset-review-director after generation or adaptation when assets will be imported into gameplay, especially for player/enemy sprites, sprite sheets, VFX, UI packs, audio cues, directional or semantic art, or anything whose readability affects the first loop.

Compatibility

Expected MCP capabilities:

• asset_forge_get_config
• asset_forge_plan_pack
• asset_forge_generate_sprite
• asset_forge_generate_sprite_sheet
• asset_forge_generate_sprite_grid_sheet
• asset_forge_generate_tileset
• asset_forge_generate_ui_pack
• asset_forge_adapt_image
• asset_forge_generate_sfx
• asset_forge_generate_music_loop
• asset_forge_adapt_audio

If one of these tools is unavailable, use the closest available MCP tool and clearly report the gap. Only use generic image generation, file downloads, or hand-authored placeholder assets when the MCP cannot satisfy the request or the user explicitly asks for another path.

Core Workflow

1. Inspect configuration.
   • Call asset_forge_get_config before a non-trivial asset task.
   • Note the default output directory, Cocos version target, asset root, overwrite policy, and exposed providers.
2. Clarify the runtime job.
   • Identify whether the asset is a placeholder, production candidate, UI element, gameplay sprite, animation, tileset, effect, or imported external source.
   • Identify target platform constraints: mobile, web, mini-game, playable ad, desktop, or editor-only prototype.
   • For a from-zero playable slice, define the minimum asset pack before implementation starts: gameplay placeholders, UI/HUD art, feedback/VFX cues, SFX, and optional short music loop. If the slice intentionally uses engine geometry only, record that as a deliberate prototype constraint instead of silently skipping the asset pipeline.
   • Apply a batch-first cost policy for generated images: related sprites, states, VFX frames, icons, pickups, enemy variants, projectiles, and props should be generated as one or more grid/contact sheets and sliced into frames. Use one-by-one sprite generation only for a style anchor, a uniquely important hero asset, or a failed cell that cannot be adapted.
3. Establish a compact art bible.
   • Capture camera/view, palette, outline style, rendering style, scale, silhouette rules, UI material, lighting, and negative prompts.
   • Reuse existing canonical assets when present instead of regenerating known characters or UI styles.
4. Select the MCP pipeline by runtime job.
5. Generate into the MCP output directory unless the user provides a project-specific output path.
6. Review outputs before import.
   • For gameplay-critical sprites and VFX, apply an explicit asset contract: role, gameplay meaning, runtime size, motion requirement, style constraints, alpha policy, collision expectation, and import target.
   • Use cocos-asset-review-director for design fit, gameplay semantics, style consistency, animation readiness, alpha/silhouette issues, mobile thumbnail readability, collision fit, audio fit, and performance risk.
   • Do not import failed production-candidate assets silently. Adapt or regenerate the smallest failed unit.
7. Import or stage assets under Cocos-friendly project folders only when requested or clearly required by the task.
8. Report exact paths, tool choices, generation settings, review status, and any rejected or deferred assets.