launch-wechat-miniprogram

Follow the four gated stages: design (requirements, MVP scope, three UI options, high-fidelity prototype), environment (account, AppID, devtools, filing), development (WXML/WXSS implementation, testing), and release (upload, trial version, review, publish). Each gate requires explicit confirmation before proceeding.

Not by default. Use plain-language checks: must data survive phone changes, be shared across users, or support uploads and admin management? If none apply, static content or local storage suffices. Tencent CloudBase is only introduced after the user confirms costs and extra steps.

No. Core visuals must map to WXML/WXSS, native components, WeUI, TDesign MiniProgram, Vant Weapp, or local images. Remote fonts, CDNs, Three.js, GSAP, and modern CSS like backdrop-filter are prohibited as core visuals because they cannot be reproduced in the mini program runtime.

It read-only checks project.config.json and app.json parsing, miniprogramRoot, page and subpackage file sets, local components, native tabBar local PNG icons, cloudfunctionRoot, referenced cloud functions, and packOptions that would exclude runtime files. Passing only counts as L1 static evidence, not compile or device verification.

The native tabBar requires iconPath and selectedIconPath pointing to real local PNG files inside the project. Network images, SVG, iconfont, and emoji are not supported. Custom tabBars are only used when native capabilities cannot satisfy the confirmed design, with extra development and testing cost.

Real payments, refunds, orders, account deletion, data clearing, and real notifications are recorded as safely skipped by default. They execute only after the user explicitly authorizes the specific target, environment, and impact, preferably in a test environment, and the authorization never extends to batch runs.