What people mean
You type intent. A model writes the files. You click. You correct in another sentence. The loop is minutes. That is the practice Karpathy named in February 2025, and the practice most AI builders now sell.
A term, not a guarantee
Vibe coding, what it means, what it does, where it stops
Vibe coding is describing the product in English and accepting running screens before you have a specification. It is a real shift in who can start. It is not a substitute for acceptance, review, or a repository you can leave. Eqlo uses that loop and still ships files you can take.
Definition
What they skip
A prompt is not acceptance. A pretty first pass can be a client-rendered shell, a second brand, or a data model you will regret. Eqlo uses the same loop and still asks you to say what is out, and to keep the repo.
Vibe coding
Building software by describing the outcome in natural language and letting a model produce running code, then steering with more language. Karpathy's February 2025 note named a habit already spreading: look at the program more than the diff. The useful reading is narrower. Vibe coding is a way to start. It is not a licence to merge every extra screen the model invents.
The prompt as a brief
A good first prompt names the user, the job, the pages or screens, and the thing that must not be there. "A booking site for a salon in Austin, three services with prices, a real calendar, no blog" is a brief. "Make me a modern platform" is a mood. Eqlo will still produce something from a mood. You will spend the afternoon deleting it. Write the constraint in the same sentence as the wish.
First pass
The version that appears in a few minutes. It exists so you can see the tree, not so you can invoice a client. Treat it as a proposal. Count the pages. Cut the ones that were never in scope. If you publish the first pass because it looked finished, you have accepted a specification you did not write.
Correction loop
A change that is a sentence: move the form, name the prices as a range, drop the testimonial you cannot defend. This is the part vibe coding is good at. It fails when you pile five unrelated asks into one message, or when you never look at the files. One change, then a click, then the next. The loop is the product. The transcript is not the documentation.
Acceptance
The test a stranger can fail. Can they book, pay, or sign in without a tour? Vibe coding will generate a happy path. Acceptance is you writing the unhappy ones: sold out, wrong postcode, a reviewer who needs a login. If you cannot name the fail, you do not have a product yet. You have a demo that claps for itself.
Scope the model invents
Dashboards, a second persona, a points club, three locales. Models pad. Your job is to refuse. "Do not add a blog. Do not add a second role." Write it once and again when it reappears. A vibe coding session that grows from four screens to twenty in an hour is not velocity. It is an unpaid roadmap.
Scaffolding
The boring structure every product needs: routes, sign-in, an empty state, a settings page that is allowed to be thin. This is where vibe coding earns its keep for people who have written forgot-password too many times. Keep the boring parts. Throw the theatrical layout. Never generate a second source of truth for a table you already run.
Clickable prototype
A flow a stakeholder can use without a facilitator. It is not a mockup and it is not production. Say which data is fake, which button is wired, and which sentence is theatre. Eqlo's prototyping page is the longer version of that split.
Handoff
The moment the work leaves the chat. A designer wants the tokens. An engineer wants the repo. A client wants a URL that does not say your name. If handoff is a ZIP of screenshots, you vibe-coded a slide. If handoff is a Git repository with a conventional layout, you vibe-coded a start another person can continue.
A repo you can leave
React and TypeScript you can clone, grep, and host elsewhere. This is the difference between a vibe and a vendor. Some tools only exist while you stay logged in. Eqlo syncs to a branch you own. You can turn the editor off. If export is a paid extra or a proprietary blob, the vibe was a rental.
Stakeholder preview
A URL per version, not a meeting to watch you drive Figma. People click. They argue about a heading. You change the heading in a sentence. That is the organisational win of vibe coding: the argument happens on the thing, not on a deck about the thing. Keep the preview off the production hostname until you mean it.
Spec versus vibe
A spec lists rules, edge cases, and what must not ship. A vibe lists a feeling and a screenshot. You can start with a vibe and finish with a spec. You cannot stay in the vibe if money or a store review is involved. The prompt history is a trace, not a contract.
Where the term came from
In February 2025 Andrej Karpathy used vibe coding for a way of working in which you steer the model by running the program. The phrase named something people were already doing in editors and in-browser builders. The term never meant the model is the engineer of record. Eqlo takes that loop and still produces files a reviewer can reject.
What it allows today
A first draft lands in two to five minutes. A publishable brochure site then takes one to two hours of back and forth. A complete mobile app is about a day. The enablement is widest when someone in the room will still say no.
A first version the same afternoon
Pages, navigation, copy, and forms from a sentence. You correct. You do not start from an empty theme.
A change that is a sentence
Select the element, write the instruction, restore the version if the change went too far. Each exchange creates a version.
A repository you can leave
React, TypeScript, and Tailwind, with GitHub sync from Plus. A rental that only exists while you stay logged in is a different product.
What it does not yet allow
It does not know the rule only one person can state. It does not pass store review because the screens look busy. Prices, medical claims, and refunds still need your name on them.
Critical systems
A proprietary bank payment or a regulated health file will need a developer to take over. Anyone selling describe a bank and ship is selling a demo.
Invisible technical debt
A prompt that accepts every extra screen hardens into soup. Open the files when you are renaming the same table twice.
Mandatory review
Generation can be wrong. Read the screens before a stranger pays. Apple and Google remain the only judges of the stores.
Vibe coding and no-code, two different things
No-code gives you a visual canvas and a vendor runtime. Vibe coding gives you language in, files out. The files might be as locked as a no-code app if the vendor keeps them. They might be a Git repository you can take to any host. That is the fork that matters. The no-code alternative page is the longer comparison.
Write a good development prompt
Start with the user and the job, not the palette. After it runs, walk public pages with JavaScript off, click the fail states, and delete what you did not ask for.
Name the user and the job
An invoicing tool for freelancers, one workspace, one invoice, one pay link. Not a modern platform.
Name the pages or screens
Home, the job, the empty state, settings. Exclude a second persona and a blog you will not write.
Name the region and the next step
European Union, United States, or United Kingdom at creation. Call, book, pay, or join. One next step.
Name what must not be there
Do not add a marketplace. Do not add a second role. Write it once and again when it reappears.
Frequently asked questions
Is Eqlo a vibe coding tool?
You describe the site or the app in English and you get running pages or screens. That is the loop. Eqlo also pre-renders public pages, can ship a native iOS and Android app from the same project, and gives you a repository. The vibe is the input. The files are the output.
Do I still need a developer?
Not to see a first version. Yes, the moment the next constraint is a system you do not run, a review you cannot sign, or a performance problem you cannot see in the preview. Handoff is a repo, not a confession.
How is this different from asking ChatGPT for HTML?
A chat window gives you a paste. Eqlo gives you a project: hosting, a sitemap, accounts if you asked, a preview URL, and files you can keep. The model is similar. The product around it is the difference.
When should I stop prompting and open the files?
When you are renaming the same table twice, when a test you can name is failing, or when a hire asks for the branch. Prompting past that point is how generated soup hardens. Open the repo. The next sentence can be "do not touch schema".
How is vibe coding different from no-code?
No-code is a canvas and a vendor runtime. Vibe coding is language in, files out. Those files are only useful if you can leave with them. Eqlo sits on that side and still ships pre-rendered pages.
Write the brief. Cut what the model adds.
Five free projects, no card. You keep the repo when the vibe has to become a product.