Vibe GuideBETA

Prepare the brief

A project description says what to make, for whom and how it is used.

What will you have after this node?
The confirmed brief is ready to copy into your project conversation.
Why this milestone?

Turn your idea into a description you can give the tool.

Start here1 step · Follow in order

0101Prepare a project briefTo checkOpen this stepClose this step
What do you want to accomplish with this project?
Turn the idea into a project brief
Review the brief, then confirm and save it
Illustration · not an app screenshot

01What do you need, and what should you keep?

What do you need before starting?

Your confirmed idea draft.

What should you keep for the next step?

The confirmed brief is ready to copy into your project conversation.

02What will this step help you do?

Turn your idea into a description you can give the tool.

Understand it, then judge for yourself

What does this concept mean?

A project description says what to make, for whom and how it is used.

How would you decide in a different situation?

Should an unrequested feature be accepted immediately, or checked against the first-version goal?

See a reference answer

Check against the agreed first-version goal; defer related but nonessential additions.

Answer in your own words; if unsure, compare the explanation above and check it against your own project.

03What exactly should you do in this step?

OpenClose

The saved idea and template below

  1. Click the template’s confirmed-material import button and check the idea.OpenClose

    Afterwards, you should see: Your previous users and goal appear.

  2. Add the name, devices and one complete use from opening to outcome. You do not need to choose a database yet.OpenClose

    Afterwards, you should see: A reader knows what to build, for whom and how to test it.

  3. Click “Confirm and generate my version”, review the result and click “Copy my draft”. If returning shows only the editor, confirm again to reveal Copy; do not replace your answers with the current template. Give the brief to your tool in the Git step later.OpenClose

    Afterwards, you should see: The confirmed brief is ready to copy into your project conversation.

Practice: personal journal (frontend + backend + database)

Use the same learning-journal project throughout this example. For your own project, compare applicable requirements without creating another project.

Fill the brief; include reading the record in a second browser connected to the same service.

What should you see after this step?
The brief requires a page, backend and database; local use does not mean browser-only storage.
What should you do first if you get stuck?
Add server restart and second-browser checks; refresh alone does not establish database storage.

04Not sure how? Follow each action

OpenClose
  1. Click the template’s confirmed-material import button and check the idea.

    What should you see after this action?
    Your previous users and goal appear.
    What should you do if that result is missing?
    Confirm the idea in the preceding step or paste the saved text yourself.
  2. Add the name, devices and one complete use from opening to outcome. You do not need to choose a database yet.

    What should you see after this action?
    A reader knows what to build, for whom and how to test it.
    What should you do if that result is missing?
    Mark uncertain conditions undecided for later discussion.
  3. Click “Confirm and generate my version”, review the result and click “Copy my draft”. If returning shows only the editor, confirm again to reveal Copy; do not replace your answers with the current template. Give the brief to your tool in the Git step later.

    What should you see after this action?
    The confirmed brief is ready to copy into your project conversation.
    What should you do if that result is missing?
    After edits, confirm again and copy the updated version.

05Words in this step

OpenClose

Project brief ↗

A description of goals, users, problems, and success conditions.

Describe occupants, rooms, and budget before renovating.

Context ↗

The conversation, files, and background available for this turn.

Documents currently on the desk are readily available.

06How should you handle a problem here?

OpenClose

Unsure how to describe the first flow

Where should you look to understand the problem?
Choose one person and one task before listing features.
Follow these steps to resolve the problem
Write “open → act → see a result”. A journal example is opening, saving a note and finding it again. Preserve unknowns.
Expected recovery
Repeat the original action and obtain the expected result; keep unexecuted checks marked unverified.

Not listed? Ask AI to investigate

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

07Material for this step (fill or copy)

OpenClose

Fill your own material below, confirm it and check the result. Follow the actions above for when to give it to your tool. If reopening shows only the editor, review and confirm again to copy.

Worksheet for this step

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.

Journal practice: fill or supplement this step

Use this as guidance for filling the template with your real information. Never copy example acceptance, costs, paths or test results.

Criteria: valid save, blank rejection, no false success while offline, restart persistence, and no duplicate from double clicking a single submission.

08Check this before continuing

The brief covers users, problem, first version, acceptance and later scope without treating examples as personal requirements.

09What should you do if the expected result is missing?

OpenClose

Confirm the idea in the preceding step or paste the saved text yourself.

Compare with an example (illustration, not your result)
Project: club reservations. Device: phone browser. Flow: view session, enter name, book, see confirmation. Budget: undecided.

Words in this milestoneIn order of appearance; open for the full explanation

References for this milestone

Open these when the question arises; they are not extra required actions.

Look up this milestone’s terms →
My project material and backups

Material stays in this browser, not in project files or AI chat. Chinese and English template drafts are separate; project selection and progress are shared. Do not enter passwords or API keys here.

Includes idea, progress, template drafts, personal checks and selection conditions, but not project code. Restore creates a new draft and preserves existing projects.

Download/import unavailable? Restore backup text

Draft and progress stay in this browser.

Complete the actions in order; expand the matching checks and remedies if you get stuck.

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.