Vibe GuideBETA
中文EN

Consult release requirements and instructions here, then return to delivery and verify the real entry point.

Does this method fit your project, and how can you check?
When would you use this method?
After acceptance, before real users receive the project.
How should you choose for your situation?
Choose local use, web or package first, then check required environment, accounts, costs, materials and recovery. Personal use need not be public.
What is easy to misunderstand?
Localhost is not a public URL. Static hosting cannot run arbitrary server programs; preview, review and release are distinct states.
How can you check that this works for your project?
Complete the core task at the target entry and record revision and recovery; unverified conditions are not passed.
Return to the action with the result →

LAUNCH

Deployment: deliver a real entry point

Deployment places a version where it can run. Release makes it available to the intended audience. Preview links, test packages, platform review, and public availability are different states.

Move forward using observed results

1. Identify the deliverable and version

For websites record the live URL; for apps record target OS and package; for mini programs record platform and version. Ask AI to identify a recoverable version and failed acceptance items.

How can you tell this item is complete?No blocking main-flow or access issues remain; a person confirms the release decision.

2. Check runtime material and costs

Ask AI to list domain, hosting, accounts, environment variables, and data services. Environment variables provide runtime configuration; secrets belong only on the server that needs them.

How can you tell this item is complete?Assign ownership for costs, renewals, quotas, and access. Fill missing inputs rather than claiming configuration is complete.

3. Check a preview or test installation

Run the complete flow with test data at the delivery location. Check new installs and upgrades for apps; verify test entry and review materials for the chosen mini-program platform.

How can you tell this item is complete?Results belong to this delivery version; local success does not replace target-environment success.

4. Approve release and check the live entry

After human approval, release and reopen or install as an ordinary user. Complete the core task and record time, version, and recovery entry.

How can you tell this item is complete?The live entry works and a failure can trigger withdrawal or restoration. Keep unreleased work labeled unreleased.

Checks are personal marks on this page, not automatic tests or saved records. Reloading clears them.

Write check results

Record actual check results

Edit the template below and confirm to prepare a copyable draft. Use it as directed by this step; sending it to AI is not required.

Complete the record → Use in the relevant step

Confirm and copy into project notes; the draft is stored in this browser. Mark unrun checks unverified, not passed.

Open troubleshooting

Choose the next step from the result

Local works but the live URL fails

Can any page open? Nothing reachable → check address, hosting status, and domain settings. Home works but subpages fail → inspect routes and asset paths. Pages work but submission fails → inspect configuration and backend requests. Fix and retest one layer at a time.

A serious issue appears after release

Pause the affected operation and preserve evidence. A tested old version is recoverable → restore and retest. Recovery is uncertain → stay paused and check data compatibility before overwriting any database.

Fill in the current situation to prepare a prompt for AI

Decision and checks for this page

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
Return to the action with this result →

Return to the matching milestone

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.