Vibe GuideUse this reference during technical planning to state constraints and ask AI to explain its recommendation before continuing the plan.
Does this method fit your project, and how can you check?
- When would you use this method?
- After scope and key interactions are clear.
- How should you choose for your situation?
- Identify storage, users, sharing, essential capabilities, budget and upkeep; assess continuing an existing project first.
- What is easy to misunderstand?
- A recommendation is not a validated design; do not add servers, login, Docker or databases for nonexistent requirements.
- How can you check that this works for your project?
- Validate the hardest capability with a small trial, then record costs, limits and the confirmed choice in docs/design.md.
Try with this project: fill material and prepare the task
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
Confirmed brief and first-version scope: [paste or provide path]
Existing project and technology: [fill in or none]
Devices, required capabilities and storage: [fill in]
Budget, deployment and upkeep constraints: [fill in or undecided]
Assess technology only without installing dependencies or modifying code. Check continuing the existing approach first; compare at most two viable options.
Explain your conclusions using these points: Recommendation, tradeoffs, unnecessary technologies, costs/limits and a minimal test of the hardest capability; wait for confirmation.TECH STACK
Choosing a stack
A stack is the set of technologies and services used to build and run a product. Describe the task, then ask AI to recommend and validate a fit.
An AI assistant builds → a stack forms the product → hosting stores or runs it. Confirm each role and cost separately.
Answer these questions before comparing technologies
No result yet. Unknowns are not treated as satisfied requirements.
What can each option do, and what does it require?
Official capability sources checked on 2026-09-23. Suitability is this guide’s assessment. Verify current prices, device compatibility, and account requirements before building.
Astro
Content-led websites with interactive parts where needed.
What limits does this option have?Shared reservations or account data require server and storage services beyond static pages.
What might you need to pay for?Domain and hosting; additional services add compute and storage costs.
Official documentation ↗React + framework
Web tools with frequent input, filtering, and state changes; ask AI to verify a specific framework.
What limits does this option have?React handles interfaces; accounts, databases, and hosting require separate decisions.
What might you need to pay for?Hosting, server, storage, and third-party services depending on the chosen setup.
Official documentation ↗React Native + Expo
A candidate for installed Android or iPhone apps after gaining Web experience.
What limits does this option have?Verify device features, offline persistence, builds, and distribution on target hardware.
What might you need to pay for?Development devices, optional cloud builds, platform accounts, and runtime services.
Official documentation ↗Tauri
Installed desktop tools using web interfaces and explicitly permitted system capabilities.
What limits does this option have?Verify system features, packages, and signing on each target OS; use copies of source files.
What might you need to pay for?Target hardware, signing, distribution, updates, and optional servers.
Official documentation ↗Prepare your requirements for AI to check
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
First check access to docs/requirements.md, docs/stories.md, docs/design.md. If missing or inaccessible, identify the prerequisite and owner action, then stop rather than invent prior work.
What device and operating system do you use: [fill in]
How much are you willing to spend on this project: [fill in or undecided]
Who will use it, and must data be saved or viewed on different devices: [local/shared, storage, cross-device or undecided]
Read requirements and interaction decisions in docs/design.md. Recommend only technology meeting confirmed scope, explaining reasons, costs, limits and data location. Prefer the existing project. Ask about essential unknowns; after confirmation save the technical section in docs/design.md, preserving interaction decisions. Do not install, initialize or implement. Record a minimal feasibility test for the hardest capability and delivery eligibility, including device/account prerequisites, expected result and alternatives. Execute after environment preparation.Resolve uncertainty
Two assistants recommend different stacks
Give both the same requirements, budget, and target devices. Different assumptions → align the inputs. Same assumptions → ask for prototypes of the same core flow and compare observed behavior, costs, and upkeep. Popularity is not validation.
Unclear whether a backend is needed
Public content only → consider pages without persistence. Data on one device → review loss and export risks. Shared or restricted data → ask AI for storage and access rules, then test two identities.