Vibe coding: build with AI without losing control of the code

AI-assisted coding can speed up prototypes, but you still need version control, tests, data protection and a way to understand and maintain the result.

Adapted from a guide first written for Quebec readers: passages specific to Quebec were removed. Rules in your province may differ.

Vibe coding describes a conversational, iterative way to build software with an AI assistant. It can help explore an idea, but generated code may be wrong, insecure or difficult to maintain. Treat every suggestion as an unreviewed change.

Keep the project understandable

1. Write a short specification and acceptance tests before asking for implementation.
2. Work in small steps and commit a known-good version before major changes.
3. Read the diff, run tests and inspect errors after each change.
4. Keep secrets, customer information and credentials out of prompts and source control.
5. Ask the assistant to explain unfamiliar code, then verify the explanation independently.
6. Test authentication, permissions, input handling, backups and failure behaviour.

Plan for maintenance

Document dependencies, build steps and known limitations. Use code review for changes that affect payments, personal data or security. Make sure you can restore the last working version and keep a human responsible for production decisions.

AI coding products and terms change quickly. Check current provider privacy settings and do not rely on generated security assurances without independent testing.

Sources and limits

Sources: software-engineering and secure-development practices, plus current AI-provider documentation. Generated code requires review and testing; this guide is not a security audit.

General information based on federal and national rules; provincial rules may differ. Confirm with the official body before acting.