Vibe GuideChoose how to deliver
Delivery means intended users can open and use it; a public URL is optional.
Why this milestone?
Choose local or shared use before preparing files and services.
Start here1 step · Follow in order
0101Choose: personal use or sharingTo checkOpen this stepClose this step
01What do you need, and what should you keep?
Your tested project and intended users.
The required preparations are clear.
Which files should AI read and save in this step?
In your tool’s project chat, ask it to open the files below. If a file is missing, follow the link back to the step that creates it.
Ask AI to read these materials first: Confirmed material and project location
Ask AI to save the result to: docs/delivery.md
Missing these materials? Return to the step that creates them →
02What will this step help you do?
Choose local or shared use before preparing files and services.
Understand it, then judge for yourself
What does this concept mean?
Delivery means intended users can open and use it; a public URL is optional.
How would you decide in a different situation?
Is the deliverable a URL, installer or local guide?
See a reference answer
Choose by intended access: URL, compatible installed artifact or repeatable local startup instructions.
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 two paths below
Send one action at a time: select and copy its prompt (⌘C on Mac, Ctrl+C on Windows), switch to your tool’s project chat, paste it, replace bracketed fields and send. Wait for the reply and check the stated result before continuing.
Choose who uses it and where: your computer, a shared URL or an installer. Fill and confirm the template.OpenClose
Afterwards, you should see: The choice matches actual use.
Use the save-in-project section to generate and send the save instruction.OpenClose
Afterwards, you should see: docs/delivery.md records users, devices and delivery method.
Ask what the chosen method requires.OpenClose
Suggested prompt:
Read docs/delivery.md. For local use explain start/stop and storage. For remote use explain where page, backend and database run, with accounts and costs. Plan only; do not publish.
Afterwards, you should see: The required preparations are clear.
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.
Choose local delivery first: one startup method, web entry and database. Public use is a later decision.
- What should you see after this step?
- You know localhost refers to the current computer; a full-stack project can be delivered locally.
- What should you do first if you get stuck?
- A friend cannot use your localhost URL; that does not prove broken code and is not fixed by disabling a firewall.
04Not sure how? Follow each action
OpenClose
Choose who uses it and where: your computer, a shared URL or an installer. Fill and confirm the template.
- What should you see after this action?
- The choice matches actual use.
- What should you do if that result is missing?
- Local use is a valid result; publication is not mandatory.
Use the save-in-project section to generate and send the save instruction.
- What should you see after this action?
- docs/delivery.md records users, devices and delivery method.
- What should you do if that result is missing?
- Request the actual saved location if missing.
Ask what the chosen method requires.
- What should you see after this action?
- The required preparations are clear.
- What should you do if that result is missing?
- localhost refers to the current computer; sharing it does not share your project.
05Words in this step
OpenClose
Build ↗
Processes source files into runnable or distributable artifacts.
Manufacture a product, then still inspect it.
Artifact ↗
Files or packages produced by a build.
The actual manufactured output.
Deploy ↗
Places software and configuration in a target environment.
Install equipment at the operating site.
06How should you handle a problem here?
OpenClose
The shared local link does not open
- Where should you look to understand the problem?
- Does it begin with localhost, 127.0.0.1, or file?
- Follow these steps to resolve the problem
- These are local entries. Choose the publishing path if sharing is needed; otherwise keep local use without adding unrelated services.
- Expected recovery
- The entry matches the intended audience.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am at “Choose: personal use or sharing”. Expected: Local work is usable, while a local address is not a public website.. Actual screen/error: [add here]. Inspect existing files first. Give one reversible action at a time, its location, and expected result. Do not recreate the project or delete existing work.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.
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.
Confirmed · personalized content ready to copy
Who will use the finished project: [fill in]
How will users open the project: [local/website/installer/other]
What device or platform will users use: [fill in]
Reason for this choice: [fill in]
Which usage or release requirements are still undecided: [details or none]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.
Record local single-user delivery with all three layers local. Future public use needs identity, isolation, persistent disk, HTTPS and costs; do not auto-deploy here. Save my confirmed scope to docs/delivery.md and local reopening instructions to README. Explain localhost means the current computer; another device cannot reach this project through that URL. Treat remote use as a separately confirmed plan.
08Check this before continuing
Local work is usable, while a local address is not a public website.
09What should you do if the expected result is missing?
OpenClose
Local use is a valid result; publication is not mandatory.
Compare with an example (illustration, not your result)
Web: URL plus running services. Desktop: compatible installer. Mobile: signed channel-specific output or store entry.
Save the confirmed record in the actual project
Complete and confirm this page’s template, then use the button below. AI saves it to docs/delivery.md; open the actual file to check it.
Words in this milestoneIn order of appearance; open for the full explanation
More troubleshooting references
Stuck? Start with what actually happens
2 situationsThese paths synthesize official docs and public reports, not frequency data. Check the symptom and verify the result.
Local development works but deployment fails
Observed symptom: Build logs fail or production assets are missing.
- What should you check first?
Inspect the first build error, runtime, build command, output directory, and filename case.
- Then resolve
Run the same production build locally, fix the specific mismatch, and verify a preview deployment before promotion.
- Verify the result
Production build succeeds and the preview completes the workflow.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am blocked at: Local development works but deployment fails.
Project and tool: [name, version, and project path]
Observed behavior: [steps, exact error, or screenshot; remove secrets and personal data]
Expected result: [actual goal]
First inspect: Inspect the first build error, runtime, build command, output directory, and filename case.
Proposed approach: Run the same production build locally, fix the specific mismatch, and verify a preview deployment before promotion.
Explain the evidence and cause before making the smallest relevant fix. Preserve existing changes and do not add features. If I must act, give one precise action at a time and its expected visible result.
Success criteria: Production build succeeds and the preview completes the workflow.
Report actual checks, unchecked items, and the next step.ReferencesVercel · Build troubleshooting ↗
Production login or API requests fail
Observed symptom: Local behavior works but production reports missing variables or redirects.
- What should you check first?
Check variable names and environment, API URL, and allowed callback domain; never print secret values.
- Then resolve
Configure the correct deployment environment and callbacks, redeploy when required, and test with a production test account.
- Verify the result
Login, data operations, and logout work on the target domain without exposing secrets.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am blocked at: Production login or API requests fail.
Project and tool: [name, version, and project path]
Observed behavior: [steps, exact error, or screenshot; remove secrets and personal data]
Expected result: [actual goal]
First inspect: Check variable names and environment, API URL, and allowed callback domain; never print secret values.
Proposed approach: Configure the correct deployment environment and callbacks, redeploy when required, and test with a production test account.
Explain the evidence and cause before making the smallest relevant fix. Preserve existing changes and do not add features. If I must act, give one precise action at a time and its expected visible result.
Success criteria: Login, data operations, and logout work on the target domain without exposing secrets.
Report actual checks, unchecked items, and the next step.ReferencesVercel · Build troubleshooting ↗Supabase · Row Level Security ↗
References for this milestone
Open these when the question arises; they are not extra required actions.
- Is delivery ready, and in what form?
After acceptance, before real users receive the project.
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.