Operator · E-E-A-T friendly truth
About vibecoding.au
The one problem we care about most
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.
A plain-English Australian guide to vibe coding — building with AI by describing what you want, trying the result, and learning where demos stop being safe for real users.
Why this site exists (the real job)
The question underneath the whole project is simple: if tools like ChatGPT, Claude, Grok, and browser builders are this powerful — how should humans use them without getting hurt or humiliated?
This is not another “best AI tools 2026” list. Those already exist. What is rarer is a human-shaped guide for using AI coding systems without burning money, drowning in logos, or deciding you are “not technical enough.”
Those systems are powerful, persuasive, and casually expensive. They make “build me an app” feel like a reasonable first sentence. It usually is not. The damage is not only messy code — it is burned credits (money), confusion, and people quitting before they ever finish one small thing they can click.
vibecoding.au says the opposite: you do not need a computer science degree. You need a smaller goal, one tool, one honest try, and a later gate before strangers, private data, or real money show up. That is how humans should use AI helpers — steer, sandbox, score, then scale — not worship the first shiny demo.
The site itself grew that way: from an empty scaffold into a clear healthy path (understand → pick a tool → first session → lab → production later). Good products often only get a spine after you have walked the content. The spine is here now. Everything else is furniture.
What this guide is (and isn’t)
This is a beginner’s path for first honest wins — plain English, one ordered route, practice in a sandbox, and a clear “later” before real users. If you only do the home page and steps 1–3, you should leave better off than when you arrived.
It is
- An ordered intro (the healthy path), not a random reading list
- A way to avoid burning credits (money) on “build me an app”
- Practice with small goals, demos, and honest pass / partial scores
- A later gate when strangers, private data, or money show up
It is not
- A full computer-science course or multi-week bootcamp
- Official support for Lovable, Cursor, Grok, or any vendor
- A security audit, legal advice, or “get rich with AI” scheme
- A promise that every demo is safe for real customers
Who runs this
Published by Ian Piggott. Personal site: ianpiggott.com. Contact: use the contact page (address as a click-to-reveal image only — anti-spam).
I am not a FAANG engineering blog and not a “get rich with AI” channel. I am someone shipping practical web projects, testing prompts in the open, and writing down what actually worked — including partials.
Independent educational resource by Ian Piggott. Not affiliated with xAI, Lovable, Cursor, Anthropic, OpenAI, Replit, Vercel, or any tool maker or AI lab.
What we have actually tested
The Prompt lab is not marketing fluff. We run briefs in real tools (including Grok Build workflows), click through the output, and score them:
- 4 pass and 1 partial human tests logged so far
- Hosted demos for comparison — e.g. Neon Grid, SaaS waitlist, Simple CRM, Habit tracker (partial on purpose)
- Honest labels beat fake five-star reviews
How this site was built
vibecoding.au is a static Astro site: content and data files, amber dark design chosen deliberately (not a clone of other portfolio looks), glossary weighted for beginners, and Grok Build used as an agentic helper with human direction and review. That is vibe coding in practice: speed with judgment.
Lesson we publish openly: open an AI agent in the wrong folder and it will edit that project. Sandboxes exist for a reason.
Who it is for
Yes
- Complete beginners who keep hearing “vibe coding” and want a straight explanation
- Founders and marketers who want a clickable demo without hiring a team yet
- Hobbyists building weekend tools
- Developers who already code and want AI speed without silent disasters
No
- People looking for “get rich with AI apps” hype
- Anyone who needs official vendor support (use the tool maker’s docs and help desk)
- A substitute for a security audit or a lawyer
What we optimise for
- Inspiration to try, not only read
- Visitor usefulness over hype
- Decision frameworks (skill × goal × constraints)
- Ethical monetisation when links or ads are used — see disclosure
Monetisation (transparent)
The site may earn from affiliate links (tool signups) and, later, ads or optional paid packs — only when content is solid enough to deserve the click. The free first-hour checklist does not require an email. Affiliate IDs stay off until programs are enrolled; placeholders are labelled.
Free resources
- First-hour checklist (print / PDF handout)
- Prompt lab
- First session
- Glossary