Your First Vibe-Code

Describe It. Watch It Happen.

Forget everything you think you know about "coding." You are not going to write code. You are going to describe what you want in plain English, and an AI is going to build it while you watch.

This lesson exists for one reason: to get you to the moment where it clicks. Where you feel the rhythm of describe, watch, adjust, repeat. Some people call it "vibe coding." Whatever you call it, the goal is to get you there as fast as possible.

---

The Workflow

Open your terminal. Launch Claude Code. And type something like:

"Make me a Python script that says hello and asks for my name."

That is it. Claude reads your project, creates a new file, writes the code, and tells you it is done. You open the file in your editor and hit the play button (which is the same as typing python script.py in the terminal). The script runs. It says hello. It asks for your name.

Now type:

"Make it tell me a joke after I enter my name."

Claude opens the file it just created, finds the right place, adds the joke logic, and saves. You run it again. It works. You just built software without writing a line of code.

---

The Debugging Loop

Something will break. That is normal. Here is the entire debugging workflow:

1. You run something and it fails. An error message appears.
2. Copy the error. Paste it to Claude. Say "fix this."
3. Claude reads the error, finds the source file, fixes it, and re-runs to verify.
4. Repeat until it passes.

That is it. Copy, paste, fix. Professional developers do this exact loop all day. The only difference is Claude handles the "find the bug and write the fix" part. Your job is to notice the error and hand it over.

---

Essential Controls

A few keyboard shortcuts make the difference between smooth flow and frustration:

Shift+Tab accepts Claude's suggested action. This is the "yes, do it" button.

Escape cancels Claude's current generation. Stops it mid-sentence but keeps the session alive. Use this when Claude is going down the wrong path.

Ctrl+C kills the entire Claude Code process. Drops you back to the regular terminal. Use this when you want to quit, not just interrupt.

/clear wipes the conversation and starts fresh. Useful when Claude starts referencing outdated context.

/resume picks up where you left off from a previous session.

"ELI5" is your friend. If Claude's output is confusing, literally type "explain like I'm five" and it will simplify.

---

The Flow State

When it clicks, when you hit the rhythm of describing something, watching it get built, tweaking it, running it, tweaking it again, you are in the flow state. This is the feeling the whole course is building toward.

Protect that momentum. Do not stop to read documentation. Do not second-guess whether you are "doing it right." Stay in the loop: describe, review, adjust, ship. The flow is the point.

---

Hands-On Exercise

1. Create a new folder on your desktop. Open it in VS Code.
2. Open the terminal in VS Code (View > Terminal).
3. Type claude to start Claude Code.
4. Ask Claude to make something fun: a greeting script, a quiz game, a random compliment generator. Something with personality.
5. Run it. Modify it. Break it on purpose. Paste the error. Watch Claude fix it.
6. When you feel the rhythm, you are done with this lesson.

---

Further Reading