vibeCode
Fast and loose. Describe what you want and let AI build it in small steps. Good for small, clear, low-risk work where you can eyeball the result.
Say it another way
vibeCoding just means describing what you want in plain words and letting the AI build it, without planning it out first. It is the quick, loose mode, great for a small experiment or a change you can check at a glance. The catch is that quick work put live as if it were finished becomes the mess you are later stuck maintaining, so vibeCode the throwaway parts and build the parts that matter with more care.
Doing this with Claude Code: vibeCode
Reach for this when the task is small and clear enough to skip planning. There is no design to settle, so you describe the change in plain language, let Claude do it directly and eyeball the result. It fits quick asks and a small clear code change, where a single step is often enough. It is the natural mode when you vibeCode a prototype and want a quick result. The skill is yours, spotting when a task is clear enough that there is nothing to plan, then going straight to building.
vibeCode fits a few cases: a quick ask, a small clear change and a prototype you want fast.
A quick ask. Count something, check if it was committed, spell-check this, there is no design to settle so you just do it.
A small clear change. One validation check in one place, where a single step is often enough.
A prototype you want fast. When you vibeCode a prototype for a quick result, eyeball it and move on.
The skill is spotting it. Knowing when a task is clear enough that there is nothing to plan is your call, then go straight to building.
Part of Ways to build it with AI.