About this skill

Problem

New WeChat Mini Program projects often stall on the boundary between idea, prototype, account setup, backend choice, device testing, and review: what to confirm first, which steps must be user-driven, which validation levels are interchangeable, and when risky actions should be blocked.

How It Works

Entry gates: Start from a rough idea, ask only route-changing questions, then move through requirement confirmation, MVP scope confirmation, UI option selection, and design approval.
Four-stage workflow: Cover design, environment preparation, development, and release, with project files instead of chat memory as the source of truth.
Safety and validation: Avoid account custody, passwords, AppSecret, and payment keys; default real payments, refunds, orders, and deletion to safe skip.
Evidence levels: Treat static checks, build, simulator, Android, iPhone, preview, and production as separate evidence tiers.

Boundaries

Useful for new projects that need a reviewable prototype, runnable app, and release checklist. Category, filing, CloudBase cost, and platform rules still depend on live official pages; the user remains responsible for identity, SMS, review submission, and final publish.

Screenshots

Use Cases

When a user starts a mini program idea, confirm requirements, MVP scope, and one UI direction.
For a partial redesign, inventory `app.json`, styles, and components before changing pages.
When choosing CloudBase, explain cost, verify `EnvId`, and compare alternatives before setup.
After a review rejection, classify category, privacy, payment, or code issues and list next actions.

Best For

First-time mini program founders who need `AppID`, filing, and device-testing guidance
Independent developers who need to turn vague ideas into reviewable high-fidelity prototypes
Small-team tech leads adding CloudBase without misconfiguring `EnvId` or unexpected costs
Mini program owners preparing review submission and handling rejection feedback