A print/PDF recipe card for one session — not software, not a course,
not required to use this site.
Why it exists
Beginners often open an AI tool, type “build me an app,” burn credits (money), get confused, and quit.
Start smaller. Use a clearer prompt. Try it in a sandbox. Finish something you can click — before the hard “real users” stuff.
Where this sits
Companion to
Step 3 · First session
— desk notes while the tool is open.
Two windows
(keep the guide open) ·
Step 4 · Lab
if you want a ready challenge instead of inventing the brief · Step 5 is later.
How to use it
Print or keep this tab open (button below).
Fill section 1 on paper first — what you’re building + must-nots —
before you open the tool (same order as Step 3).
Tool in a second tab · paste the prompt once · tick as you go · stop.
Print tip: “Save as PDF” in the browser print dialog. Offline copy:
single HTML file
(same content — re-download after site updates).
Desk handout · vibecoding.au · v1.2.4
Your first session of vibe coding
Purpose: finish one small thing you can click — not a full product. Ian Piggott · educational only (not legal
or security advice). Pair with Step 3 on the site.
1. Before the tool (do first)
□ Set a timer for 30–60 minutes
□ Write one sentence: what I’m building today (e.g. bakery contact page / todo list / tiny game) — not “full
app”
□ Write 3 must-nots (AI adds extras if you don’t fence them — e.g. no accounts · no fake stats · no payments ·
no dashboards · don’t paste real private info into the chat)
□ Plan a new empty project only (sandbox — not important work)
□ Glance at free-tier limits (credits often mean money) — don’t study every paid plan mid-build
□ Optional: fill the prompt below in Notes so you can paste once
2. When you start the clock
□ Tool in a second tab; this sheet (or Step 3) still open
□ New empty project → paste prompt once
□ Stay on one click-path start→finish before asking for extras
□ Fix one problem at a time (short follow-up: only that bug)
□ Jot: what works / what’s still shaky · close the tool · stop
3. Prompt (CONTEXT · SCOPE · CONSTRAINTS)
Paste the whole block into the tool. Edit to match what you’re building.
CONTEXT:
I am a beginner. Today I only need: ____
SCOPE:
Build only: ____
Must include: ____
CONSTRAINTS:
- No accounts / no fake stats / no payments (edit as needed)
- Works on a phone-width screen
- Do not invent features outside SCOPE
- At the end, list anything I should double-check
--- example (todo list) ---
CONTEXT:
I am new to vibe coding. Today I only need a simple todo list I can use on my phone.
SCOPE:
One page: add items, tick done, keep list after refresh, friendly empty message. Phone-width layout.
CONSTRAINTS:
No sign-up. No fake stats. No payments. No dashboards. Keep it simple.
4. Score yourself
Score
Meaning
Pass
You can click through the main thing without constant fail
Partial
Core idea works; messy or incomplete — still a win
Fail
Broken or you understand nothing — make the brief smaller and try again
5. Done for today when…
□ Main thing is clickable (even if rough)
□ You know which tool you used (practice project)
□ Short notes: works / still confusing
□ You stopped — no credit-burning polish spiral
6. Later only (not night one)
Real users / private data / money →
Step 5 · production
(educational notes, not professional advice).