"Vibe coding" means building a program, a website, or a small app by describing what you want to an AI, which writes the code for you. You say "I want a page with a contact form," the AI produces the files, you test, you adjust.
It's real, and it's within reach of people who have never coded. But there's a huge difference between steering the code and being dragged along by it. Here's how to stay on the right side.
The four families of tools
Without naming names, since they change fast, tools fall into four families:
- Chat: you ask an assistant (ChatGPT, Claude, Gemini…) for code and copy it yourself.
- In-browser app builders: you describe, they generate and host a complete app.
- AI code editors: a real editor, like the ones developers use, with a built-in assistant that edits your files.
- Terminal coding agents: you hand them a task, they read the project, edit several files, and run commands.
To get started, families 1 and 2 are enough. Families 3 and 4 become useful once your project grows.
The six words to know
With these six words, you can follow any tutorial:
- File: code lives in files, and each one has a role.
- Terminal: the window where you type commands.
- Dependency: a piece of code written by others that your project uses.
- Commit: a named save point in your project.
- Diff: the exact list of what a change modified.
- Deployment: putting it online.
Rules for steering, not being dragged along
Ask small
Three small requests you've reviewed beat one big request you just accept. A good request produces a change you can review in a few minutes. "Add a button that submits the form," not "build me a full site with payments and a members area."
A plan before the code
As soon as several files are involved, ask for a plan first: "Explain what you're going to change, file by file, without writing any code." You approve, then the AI codes.
Keep only what you understand
Never keep a line you don't understand at all.
Ask the AI to explain it. If the explanation doesn't hold up, the line goes.
The AI proposes, the test decides
The AI may claim everything works. Only the test counts: you open the page, you click, you check.
The two-strikes rule
If the AI fails twice on the same bug, don't ask for the same thing again. After two failures, you diagnose: "List three possible causes and how to check each one, without changing the code."
Save often
A good commit is a save point before the boss fight. With a clear message ("add contact form"), you know where to go back when something breaks.
Security, even for a small project
Three classic traps:
- Secrets in the code. An access key for a service must never be written in a published file. If it leaks, revoke it immediately.
- Made-up packages. An AI may suggest installing a dependency that doesn't exist, or whose name imitates a real package. Check before installing, never after.
- Going live without review. Before publishing: no secrets, known dependencies, diff reviewed, test passed.
Where to start
Start with a page, not a castle. A page for a local club, an online résumé, an event page. Something small, useful, and easy to show off.
That's exactly the path of Forge island on Ovrelia: a first page, the plan-test-review method, then Git and going live, and finally secrets. The first chapter, "From chat to editor," is free, and you fix your first bug right in the browser: get started.
Going further
Want to try tonight? The guide to coding with AI without being a developer has you build a single-file page, with prompts to copy. To choose and scope a more ambitious project, read how to nail your first AI project. And to test your reflexes, start the friend challenge: ten timed questions about AI, and a score for your friends to beat.
Frequently asked questions
Do you need to know how to code to do vibe coding?
Not to start a small page. But you need to learn to read what the AI proposes, to test, and to keep only what you understand; otherwise the code drives you instead of you driving it.
Is vibe coding suitable for a real application?
For a prototype or a simple page, yes. As soon as there are accounts, payments, or personal data, you need solid security knowledge or help from a developer.
What should I do when the AI goes in circles on a bug?
Apply the two-strikes rule: after two failed attempts, go back to the last version that worked, describe the problem differently, or break it into smaller pieces.
What project should I start with?
A single, useful page: a page for a local club, an online résumé, an event page. Small, easy to show, and easy to test.