The standard prompt template assumes you know what a tech stack is. This tool doesn't. Answer five plain-language questions and we'll build the complete prompt for you — ready to paste into Claude, Cursor, or Bolt.
What you'll answer
01 What you want to build
02 Who it's for
03 The one thing it must do
04 How technical you want to go
05 Any constraints
Nobody should be stopped from building their first thing by a prompt template they don't understand. This tool is free, always.
FREEAlways free — no purchase required.
Step 01of 05
What do you want to build?
Describe it the way you'd explain it to a friend — not a developer. Plain English only. One or two sentences is perfect.
Why this matters
The AI needs to understand the what and why before it writes a single line of code. A clear plain-English description produces better results than any amount of technical specificity.
Example
"A simple tool that lets me track which of my freelance clients have paid their invoices. I want to see at a glance who owes me money and how much."
Don't worry about being too simple. The AI will ask clarifying questions if it needs more.
Step 02of 05
Who is it for?
Not "users" — a real person or group you can picture. The more specific you are, the better the AI understands what the tool needs to do.
Tip
If it's just for you, say so. "Just me — I'll use it daily on my laptop" is a completely valid answer and actually helps the AI skip things you don't need (like user accounts, mobile screens, etc).
Examples
"Just me — a freelance designer who invoices clients monthly."
"My small team of 4 — we share a Google Sheet now but it's getting messy."
Step 03of 05
What must it do?
Name the two or three things that make this tool useful. Not everything you might eventually want — just what it must do on day one to be worth using. Three maximum.
The golden rule
Start smaller than feels right. Every feature you add roughly doubles the complexity. The fastest path to a working tool is one feature that works perfectly, not four features that half-work. You can always add more after.
Example
1. Add a client with their name and invoice amount 2. Mark an invoice as paid 3. Show a dashboard of who still owes me and the total outstanding
1
2
3Optional
Step 04of 05
How technical do you want to go?
This determines what kind of tool the AI builds. There's no wrong answer — each has real advantages. Pick the one that matches where you are right now.
What is a "tech stack"?
A tech stack is just the set of tools and languages used to build something. You don't need to choose one yourself — if you select "Keep it simple," the AI will pick the most straightforward option and explain its choice. You can always change it later.
Not sure of the exact name? Just describe it: "something Python-based" is fine.
Step 05of 05
Any guardrails?
These are instructions that tell the AI what to avoid. All of them are pre-selected with the sensible defaults for a first build — untick anything that doesn't apply.
Why guardrails matter
Without constraints, AIs tend to over-engineer. They'll add login systems, databases, and extra features you didn't ask for. These defaults keep the first build focused and fast.
Anything else the AI should know? (optional)
✓ Your prompt is ready
Copy it. Paste it. Build.
This prompt is ready to paste into Claude, Cursor, Bolt, or any AI coding tool. You don't need to change anything — but you can edit it directly in the box if you want to tweak the wording.
Your first vibe coding prompt
What happens next: Paste this into Claude (claude.ai) or Bolt (bolt.new) and press send. The AI will either ask a clarifying question or start building immediately. Either response is good — answer any questions plainly, then let it run.
Where to paste this
Claude
claude.ai — best for plain conversation, reasoning, and understanding what gets built.
Bolt
bolt.new — builds a live preview in the browser. Best for visual tools you want to see immediately.
Cursor
cursor.sh — best if you've built anything before. More control, more power, small learning curve.