How PreVibe turns one sentence into working software
You don't need to write a full spec to get started. Drop a sentence, click Vibe, review what comes back. Here's how each piece of the studio works.
From install to your first Vibe — the shortest path
If this is your first time with PreVibe, follow this path and keep the friction low.
A new project and Quick Start doc are created automatically — ready to go out of the box.
Free runs on local Claude Code or Codex. Pro and Max can switch to the PreVibe proxy.
No full spec required. A sentence about what you want to build is enough. Vibe grows it from there.
AI proposes changes from your current document and project context. You review and decide.
The three canvases inside every PreVibe project
You don't need to fill them all out on day one. They grow as you Vibe.
A practical way to organize docs
You do not need every detail on day one. You only need to make this round of work explicit.
.previbe-docs/
Product Docs/
Quick-Start.md
Requirement Document.md
Agent Context/
CLAUDE.md
Project rules.mdBest for onboarding. It helps you understand the product loop before you move into a real project requirement.
- Faster onboarding
- Learn the loop before real delivery
The main document for real work. Define users, goals, scope, constraints, and priorities here before each push forward.
- Clearer scope
- Every Vibe run keeps working from it
Store durable rules here: tech stack, coding standards, system boundaries, deployment rules, and other repeated instructions.
- Keeps long-term rules stable
- Reduces repeated explanation
How Free, Pro, and Max map to runtime choices
These are not separate products. They are three plan sizes for the same workflow.
Best for validating whether the creation loop works for you. You still get the full Vibe, Review, Run, and History workflow.
- Runs on local Claude Code or Codex
- Good for first-time use or lighter projects
- Start with a free download
Best for people pushing projects every day and wanting less runtime friction. Billing, credits, and mode switching stay in the desktop app.
- Unlock PreVibe proxy credits
- Switch between Proxy and Local
- Better fit for ongoing development
Best when your daily usage and task concurrency are clearly above normal paid usage and you need more headroom.
- Everything in Pro
- Higher limits for heavier usage
- Priority handling during busy periods
What one Vibe cycle looks like
The point is not that AI wrote code. The point is that you directed what happened.
Let the document define the job before AI starts writing anything from a vague prompt.
AI output becomes proposed work first. You accept, reject, or ask follow-up questions before it lands.
Build and inspect the project in the desktop app so you know whether it actually works.
Start with a sentence. The studio grows from there.
If you haven't installed PreVibe yet, download the desktop app. If you already have it, drop a sentence and click Vibe.