cocos-wechat-local-build

Cocos WeChat Local Build

Overview

Use this skill for the local-only Cocos Creator to WeChat Mini Game loop: project readiness, build config, wechatgame command-line build, output inspection, and local simulator/debug preparation. Do not handle upload, review, release, payment, or production operations with this skill.

Target Cocos Creator 3.8.8 when the local machine has it installed; otherwise detect the configured Creator path.

Core Workflow

1. Detect environment.
   • Prefer cocos_local_get_environment when the Cocos local MCP tools are available.
   • Confirm Cocos Creator path, WeChat DevTools CLI path if needed, and target project root.
2. Inspect the project.
   • If starting from zero and no project exists, use cocos_local_create_project to create a Cocos Creator 3.8 project from the built-in empty-2d template and create assets/scenes/Main.scene before build preparation.
   • Use cocos_local_inspect_project when available.
   • Check for assets/, settings/, scenes, scripts, existing build output, and project metadata.
3. Prepare build config.
   • For generated starter projects, use cocos_local_open_project, cocos_local_wait_for_editor_bridge, and cocos_local_apply_scene_blueprint to prepare an active saved scene before creating the final build config.
   • Reuse an already-open Cocos Creator process for the same project when possible. If old projects are still open from earlier tests, close them or use distinct editor bridge ports before trusting scene or build preparation evidence.
   • Before creating the build config, declare the target device class, orientation, design resolution, and fit policy. For phone-first WeChat Mini Games, prefer an explicit portrait design resolution such as 720x1280 or a project-proven equivalent unless the game design requires landscape.
   • Use cocos_local_create_wechat_build_config for a reproducible config JSON.
   • Pass designResolution when the MCP tool supports it. If the tool does not support it, patch the generated config or report the missing adaptation setting instead of silently building with a desktop/template default.
   • When a scene asset is known, pass startScenePath such as assets/scenes/Main.scene so the MCP reads the UUID from the .meta file.
   • Use placeholder appid only for local non-platform gameplay checks; ask for a real appid before testing WeChat APIs.
4. Build locally.
   • Use cocos_local_build_wechatgame with configPath when available.
   • Prefer dry run first when the project, appid, or Creator path is uncertain.
5. Inspect output.
   • Use cocos_local_check_wechat_build_output for required files and package budget warnings.
   • Confirm game.json and project.config.json exist under the built wechatgame folder.
6. Audit local runtime package risk.
   • Use cocos_local_audit_runtime_package before opening the simulator when the tool is available.
   • Review package budgets, largest files, oversized textures/audio, and first-package pressure.
   • Treat this as static risk analysis; it is not FPS, memory, or gameplay verification.
7. Open or prepare WeChat DevTools locally.
   • Use cocos_local_open_wechat_devtools to open the local build/wechatgame output.
   • Use cocos_local_preview_wechat_devtools only when preview artifacts are useful for local/debug review.
   • Use cocos_local_manage_wechat_devtools for cache cleanup, closing the project, or quitting DevTools.
8. Collect runtime evidence.
   • Use cocos_local_collect_runtime_evidence after observing launch, first input, core loop, result/failure, restart, and logs.
   • Keep build success, DevTools opening, and runtime verification as separate states in the final answer.