WeChat DevTools Workflow

Problem

WeChat DevTools workflows split across CLI, windows, project config, simulator, cloud environment, and upload confirmation. When an agent guesses commands directly, it can hit command not found, expired login, tokenRequired, unconfirmed async taskId, or cross-scene tool misuse.

How it works

The skill treats the WeChat DevTools workflow as a single entry point, assuming wechatide is already available locally. Key steps:

• Check status first: before the first call, run check_wechatide_status and inspect versionRelation, loginExpired, and tokenRequired.
• Route by intent: initializer for project windows and login, project-manager for project list, project-config for project.config.json, compiler for compile and refresh, previewer for preview and upload, automator for page automation, debugger for diagnostics and screenshots, cloudbase-operator for cloud functions and resources.
• Respect async rules: actively poll only for login or auth tasks; for upload, deletion, cloud writes, and preview confirmation, record taskId and wait for user confirmation instead of resending.
• Carry context across scenes: pass project, confirmed, blocker, and pendingTask when switching scenes, avoiding duplicate window opening or repeated status checks.

Boundaries

Use this when the current project is clearly a WeChat mini program or mini game, and the goal is compile, preview, upload, login, project configuration, page automation, runtime diagnostics, screenshots, log inspection, or cloud environment work. Avoid it for general coding assistance, desktop automation unrelated to mini programs, or unregistered tool calls. Reuse confirmed token, project path, and async task state instead of guessing retries.