WeChat Mini Program Internationalization

Problem

When WeChat Mini Programs serve users outside mainland China, common blockers are not missing features but local assumptions: phone fields accept only +86 and 11-digit numbers, names allow only Chinese characters, ID types only include national IDs, and fixed-width UI containers overflow after English, Spanish, French, or German translation. These P0 issues can break registration, identity verification, order, or support flows.

How It Works

The skill drives fixes by P0 -> P1 priority. It first runs a project scan and produces validation/reports/scan-report.md and scan-result.json, then gives code-level guidance across three areas: account systems, form input, and UI layout. For accounts, it checks international dialing codes, number lengths, email verification fallback, and global SMS channels. It recommends WeChat's quick phone verification component when available, or dynamic validation by country code for custom selectors. For forms, it broadens name rules to Chinese characters, letters, spaces, hyphens, and apostrophes, and extends ID types to passports, permanent residence cards, and Hong Kong/Macau/Taiwan travel permits. For UI, it uses wx.getAppBaseInfo() to hide marketing popups, viral sharing, and points tasks for non-Chinese users, then flags fixed width, fixed height, !important, and missing word-break patterns. Overflow risk is rated HIGH, MEDIUM, or LOW based on estimated translated text width relative to container width.

Boundaries And Notes

This is best for WeChat Mini Program front-end experience adaptation, especially overseas access, bilingual titles, identity forms, and multilingual UI. It is not a complete back-end internationalization solution; global SMS, email verification, secret management, and rate limiting still require backend and security controls. Scanning dependencies must be installed; if Cannot find module 'fast-glob' appears, install dependencies in validation before running the scan.