Vibe coding at work: from a prototype written by AI to software you can put in production
You built a prototype by describing it to an AI, and you want to put it in production. What a review usually finds, the grid to fill in with a developer before going live, and who answers for the software once it ships.
The sandbox
The prototype
Written by AI, on dummy data, with no real credentials
The grid, together
Data, users, secrets, dependencies, tests, way back, what comes next
The review
By a developer, with reviewed tests
The pipeline
Analysis, checked dependencies
Production
Approved by a person, a way back ready
Vibe coding means having AI write software by describing what you want, without reading the code it produces. The term was coined by the AI researcher Andrej Karpathy in February 2025. For a prototype, the gain is real; for a tool others will use, that touches your data or your customers, review, tests and checks have to come back in.
This guide is for you if you built a prototype this way, an internal tool, a mock-up, a small application, and want to put it in production. It says what a review usually finds, gives the grid to fill in with a developer, and who answers for the software once it ships.
What your prototype does well, and what it does not tell you
It shows precisely what you want: the screens, the flow, the business rules. It is the best specification a developer can receive. What it does not tell you: whether the data is protected, whether the libraries it uses exist and are safe, what happens when two people use it at once, and who will fix it when it breaks.
What a review usually finds
- Security flaws. The vendor Veracode tests AI models on the same coding tasks every year: in July 2026, the code produced passed its security tests 56% of the time on average, against 55% a year earlier.
- Invented dependencies. Models suggest packages that do not exist, and attackers publish malicious packages under those names: this is “slopsquatting”, which CERT-FR reported as in use in its February 2026 threat summary.
- Secrets in the code. An access key pasted in to make it work, which leaves with the code.
- Actions without a guardrail. In July 2025, the agent of a vibe coding platform deleted production data during a code freeze, in a public trial.
What review found in our own films. Our presentation films are written in code with an AI assistant, by describing what we wanted. Their review found two defects, noted along the way: fonts loaded in the wrong place in the code, and the rendering tool’s mark to remove from the picture. Nothing serious, but the first one only shows when you read the code: describing what we wanted was not enough.
The go-live grid, to fill in together
You, who know the need, and a developer, who knows the code, fill in this grid together before any release:
Question | You answer | The developer checks |
|---|---|---|
The data | Which data the tool reads and writes; any personal data? | Where it is stored, who can reach it, how it is protected |
The users | Who will use it, besides you | Authentication, each person’s rights |
The secrets | Which accounts and keys the tool uses | No secret in the code; a secrets manager |
The dependencies | Nothing: that is their part | Each package exists, comes from a known source, at a pinned version |
The tests | What must work, and what must never happen | Tests that check it, reviewed by a person |
The way back | What you do if the tool stops | How to go back to the previous version, and the backups |
What comes next | Who asks for changes | Who fixes it when it breaks, and in which delivery pipeline |
As long as one line has no answer, the release waits: the prototype stays in its sandbox, and that line becomes the next piece of work.
Who is allowed to release to production?
Everyone can prototype, in an isolated environment, with no production data or real credentials. Whatever goes to production follows the same path as the rest of the code: review, tests, analysis and a person’s approval. The rules for framing the agent that writes the code are in our article on rolling out coding agents, and the pipeline checks in our article on DevSecOps.
Who answers for it: our reading
Two European texts matter here. The new directive on liability for defective products (2024/2853) counts software among products, for those placed on the market after 9 December 2026: defective software that causes damage engages its manufacturer. The Cyber Resilience Act makes manufacturers responsible for the security of products with digital elements, with obligations that apply in full in December 2027.
Our reading, which is not legal advice: the company that makes the software available answers for it, however the code was written. The AI does not become liable in its place, and “the AI wrote it” is no defence for anyone. Hence three records to keep for every release: who reviewed, which tests passed, who approved. For an internal tool, these texts do not apply in the same way: have your case checked by your lawyer, your other obligations (personal data, security) remaining whole.
From prototype to product, step by step
- Keep the prototype as a living specification, shown to users.
- Fill in the grid together, and deal with each line left unanswered.
- Have a developer review and, if needed, rewrite what goes to production.
- Add the missing tests, and go through the full delivery pipeline, with its security analysis.
- Release behind a person’s approval, with a way back ready.
Our page Automate software development shows how AI agents take their share of the cycle with human review at every step, and the offer Flaws caught before release sets up the pipeline checks. See also the page Agentic AI.
Frequently asked questions
Can AI-generated code go to production?
Yes, if it passes the same checks as hand-written code: review, tests, security analysis and approval before release.
Who is responsible for that code?
The company that makes it available, in our reading of the European texts, which is not legal advice: they target the software’s manufacturer, however it was written. Hence the importance of keeping track of who reviewed and approved what.
Should vibe coding be banned for non-developers?
No. Give them an isolated environment, with no production data or real credentials. Their prototypes serve as a starting point for developers, but do not go to production without them.
Sources
Written with an AI assistant from the sources cited, facts checked and reviewed by Mehdi Chafik on 26 October 2026.
- Andrej Karpathy, X post coining the term, February 2025.
- Veracode, 2026 GenAI Code Security Report, 28 July 2026.
- CERT-FR, threat summary CERTFR-2026-CTI-001, 4 February 2026 (in French).
- AI Incident Database, incident 1152, July 2025.
- Directive (EU) 2024/2853 on liability for defective products, 23 October 2024.
- European Commission, liability for defective products.
- European Commission, Cyber Resilience Act.