Vibe GuideBETA
中文EN

Understand the capabilities this project type needs and take relevant features back to the project brief.

Project typesMini programs
MINI PROGRAM DEVELOPMENT

Build where the users already are.

A small app that runs inside WeChat, Alipay, or Douyin. Pick one platform first and solve a specific problem for its users.

One platform first
Mini programs
Event information & sign-up
Start here →
INTERFACE EXAMPLE

Check suitability before building

01Which projects fit this form?

Sign-ups, bookings and member services with an existing audience on WeChat, Alipay or Douyin, when the platform supports the required features and account eligibility.

02What should be ready before you start building?

Builders who can choose one platform, reach its real users, and check account eligibility, permissions, review and release requirements.

03Which projects should consider a different form?

Projects needing a universal link across unrelated platforms, or capabilities unavailable on the chosen platform. Code and eligibility are not automatically portable between platforms.

04Which missing prerequisites should you resolve first?

Builders without a known platform audience or required account eligibility, or who cannot accept platform review and constraints. Resolve these before implementation.

Still unsure? Try a small validation

Check needed features and test access using the actual account, then preview one small action. Record missing eligibility; a simulator preview is not a public release.

If the audience is not tied to one platform, compare a shareable web app.

Compare an alternative →

This reference helps choose project form; its sections are not a second required route. Return to “Prepare the brief” on the main route to update the brief; technology selection is still “Agree on design and technology”.

Start with a small first version

01 / START
FOR EXAMPLE · AN ILLUSTRATION

Event information & sign-up

View an event, pick a session, enter details, and see the result. Start with this one flow.

Choose one platform first

For people using WeChat. Check its current official account and release requirements.

Three things to prepare

  • Choose the platform the users use
  • Check current account and feature requirements
  • Event content and sample data

The route from idea to product

02 / BUILD

Finish one small step, check it through actual use, then move on. Open each step to see the expected result.

01Choose one platform

Find out where the users are. Don’t target three platforms at once.

Afterwards, you should see: One target platform.
02Check the prerequisites

Check the account, documents, and allowed features.

Afterwards, you should see: A clear list of what is possible and what is missing.
03Build the core flow

Make viewing an event, signing up, and seeing a result work.

Afterwards, you should see: A small version to preview.
04Try it inside the platform

Check real storage, declined permissions, and access for different people.

Afterwards, you should see: Actual results, not just preview screenshots.
05Prepare and submit

Prepare the name, icon, and description required by the platform.

Afterwards, you should see: Materials that match the actual product.
06Check the live entry point

After the platform’s checks, release it and try the live entry point.

Afterwards, you should see: The users can complete a sign-up.

Ask AI to check project fit

03 / PROMPT

Assess the form, without building

Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.

Plain text · Add actual material before sending to AI

After choosing: update the brief and follow the guided route →

What to check when stuck

Development preview works but the platform does not

Repeat the main flow with the same test account inside the selected platform and record the failing step.

  • If it completes, check other identities and the release entry; preview success is not a release.
  • If it fails, check account eligibility, allowed features, and request configuration against that platform’s official rules.
Does review submission mean release is complete

Does the platform explicitly show a released version and provide an entry ordinary users can access?

  • Complete a sign-up from the release entry as a non-developer and record the result.
  • Under review or pending release → keep status unreleased, address feedback, and await a release decision.

Record the version, device, test data, steps, expected outcome, actual result, and failures. Keep AI execution records separate from personal trial results.

Open the hands-on acceptance and release template →

A few useful terms

04 / UNDERSTAND
Mini program
An app that runs inside an existing platform.
Permission
A person’s consent to share data or allow a capability.
Review
The platform’s checks before a version is made available.

Find the starting point

Module shortcuts

What people build · AI revenue research · 50 ideas · GitHubComplete roadmap · idea to releaseWrite down the ideaI only know I want a websitePrepare a project briefUnsure how to describe the first flowOpen an AI tool that can edit filesInstallation, sign-in, or the screen differsCreate a folder for the projectDocuments or the folder is missingOpen that folder in the AI toolAI names a different projectCreate Git history and project instructionsCommit fails or asks for identityInspect a file AI actually createdPrevious files are missingAnswer one question at a timeAI asks about unfamiliar technical termsChoose only this version’s essentialsReducing scope left only a pictureKeep the agreement in plain languageThe document is too long to reviewDescribe how people will use itAI lists features without a user flowReview a key screen before buildingThe prototype may use simulated behaviorLet AI choose from actual conditionsI do not know local versus shared storageAsk AI for the next small taskThe first task just says “build frontend”Check the runtime and start the projectInstallation or startup failsOpen the first page of the projectThe preview will not openAdjust this page onlyA visual edit changed other behaviorMake Save retain real contentCannot save, or records vanish on refreshFinish the whole flow onceThe button responds but nothing happensTry blank input and repeated clicksBlank or duplicate records appearReopen it after stoppingThe address fails the next dayCheck it against the original ideaAI says done, but I cannot use itRecord the trial feedbackThe issue happens intermittentlyPlan the fix and its passing checksAI starts fixing without a planFix according to plan and hand back for retestingThe same action still fails after a claimed fixChoose: personal use or sharingThe shared local link does not openAssess readiness for deliveryReadiness is claimed without evidencePrepare and try the deliverableInstaller or deployed application failsApprove delivery and verify the real entryIt opens locally but not for othersOptional: publish a simple page on GitHub PagesThe public URL returns 404Continue next time without starting overAI wants to start over in a new chatChoose a tool · Codex Claude Cursor Qoder TRAE Kimi pricingHomeProject typesTalking to agents · prompts and troubleshootingChoosing a stackFrontend & UI · component dictionaryGlossary · AI and development · examples and diagramsOpen the tool and verify project accessPrepare the project, version history, and AI rulesDescribe the intended interface styleHelp AI change exactly one targetBackend: storage and accessTesting: check that it worksDeployment: deliver a real entry pointMaintenance: keep the product usableWebsites & web apps · The idea, one link away.Mini programs · Build where the users already are.Mobile apps · Turn a good idea into an everyday app.Desktop apps · Make a tool for repetitive tasks.

A practical guide for beginners

This bilingual practical guide has 6 stages, 18 milestones and 31 actions. App illustrations are examples; users verify their own project results.