Vibe GuideBETA
中文EN

Use this guide to record the current state and next task so AI can continue from the existing version.

Does this method fit your project, and how can you check?
When would you use this method?
After delivery or before another change.
How should you choose for your situation?
Record startup, account/billing owners, backup/recovery and the next task; distinguish defects from new requirements.
What is easy to misunderstand?
A backup file does not prove restoration. Previous tests do not validate an update; keep a recoverable version and test data changes on copies.
How can you check that this works for your project?
Restart from the record, restore test data and check the main flow and costs after the next update.
Return to the action with the result →

OPS

Maintenance: keep the product usable

Maintenance looks after operation, costs, data, and updates after release. Keep an actionable record instead of treating launch as the end.

Move forward using observed results

1. Recheck the main flow

Choose a check schedule based on real usage. Record the live entry, version, and a test result. On failure, identify affected users and whether to pause.

How can you tell this item is complete?Do not claim healthy operation without a check or improved outcomes without real usage data.

2. Track costs and expiry

Record owners, billing links, renewal dates, and budgets for domains, hosting, accounts, storage, and third-party calls. Ask AI to organize reminders.

How can you tell this item is complete?Rely on reminders only after they are actually configured. Inspect bills and usage before upgrading a plan.

3. Prove backups can restore

Restore a test backup in isolation and verify counts, sample contents, and access rules. Record backup frequency, retention, and restoration time.

How can you tell this item is complete?A backup file alone is not a successful restore; another maintainer should be able to repeat the process.

4. Separate bugs from new requests

A goal cannot be completed → investigate and fix. A new capability is requested → return to scope confirmation and assess costs and data changes before planning.

How can you tell this item is complete?Preserve a recovery version for updates, retest the main flow, and record real feedback.

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

The bill suddenly increases

Compare time and usage: usage rises too → identify the feature or traffic and set limits according to budget. Usage unchanged → inspect plan, renewal, and line items. Request missing bills instead of guessing.

A backup exists but recovery is unclear

Copy it into an isolated test environment and check format and recovery tools. Restore works → verify content and access, then document steps. Restore fails → preserve current data, inspect completeness and compatible versions, and avoid overwriting production.

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.