IKANGAIVibe Support
All notices
Upkeep

The app works, until you need to change it

For everyone who builds with AI

Does this apply to you?

Tick anything that is true for you. If nothing is, you can skip this notice.This applies to you. Go to the steps

What is the problem?

Building with an AI tool feels fast because you skip the planning. The cost arrives later. The first time you want to change something, you find you cannot explain how the app works, so you cannot tell the AI what to keep, and each fix breaks something else.

Corey Gallon, whose talk this notice is based on, calls it the vibe coding hangover.

What could happen?

You add one feature and an older one stops working. You cannot tell whether a change is finished, because nothing was written down about what finished means.

In the end it is quicker to start again than to repair, and you lose both the work and what you learned from it.

What should you do?

4 steps · 1 message to paste
  1. Message to paste
    Before you write any code for this feature:
    1. Restate it as one sentence: who wants to do what, and why.
    2. List what is in scope now and what is explicitly not.
    3. Tell me how we will know it is done: the tests you will run, what I should see on screen, and that the logs show no errors.
    4. If this is really more than one feature, split it and do only the first.
    Wait for my OK. When it passes all of step 3, commit only this feature's changes and tell me what you committed.

Where this comes from

Corey Gallon, Rexmore. The Cure for the Vibe Coding Hangover. AI Engineer Code 2025.

How we adapted it

This is a cut-down version of his method, which runs to ten principles and a five-step planning process over 57 minutes. We added nothing of our own.

Published . Last checked against the source on .