Pebellslearn by building
RoadmapsMatrixCoursesSandboxSign in

Course details

Vibe Coding

Learn to build software by describing what you want to an AI coding assistant, without handing over your judgement. You will plan in thin slices, write clear prompts, read and test the code you get back, debug with evidence and catch security mistakes before they ship. The whole course follows one small app, Kitty, where flatmates share costs.

Ready to learn6 sections · 23 lessons
Start learning

Course curriculum

What Vibe Coding Is4 lessons

Meet the vibe coding loop, the kinds of AI coding assistants, the owner's mindset that keeps the work honest, and the signals that tell you to stop prompting and take over.

  1. What Vibe Coding Is12 min
  2. Kinds of AI Coding Assistants10 min
  3. You Own Every Line12 min
  4. When to Take the Wheel12 min
Plan Before You Prompt4 lessons

Write a one-page spec, cut the work into thin slices you can demo, choose a stack you can read, and read every piece of code you accept.

  1. Write a One-Page Spec12 min
  2. Slice the Work Thin12 min
  3. Choose a Familiar Stack12 min
  4. Read the Code You Accept15 min
Prompting and Context4 lessons

Describe intent with a goal, rules, an example and a check, ask for one change at a time, choose the right context, and keep long sessions from drifting.

  1. Describe Intent Clearly12 min
  2. One Change per Prompt12 min
  3. Give the Right Context12 min
  4. Keep Sessions Fresh12 min
Version Control and Testing4 lessons

Commit before each change, review the diff before you keep it, choose your own test cases, and stop an assistant from bending the tests to fit the code.

  1. Commit Before You Prompt12 min
  2. Review the Diff Before You Commit12 min
  3. Test What It Should Do15 min
  4. Guard the Tests15 min
Debugging with an Assistant3 lessons

Turn a vague bug report into a failing test, read an error yourself before prompting, and escape the loop where every fix breaks something new.

  1. Reproduce Before You Fix12 min
  2. Read the Error First12 min
  3. Break the Fix Loop15 min
Security Basics4 lessons

Keep secrets out of code and prompts, treat every input as hostile, check who can see what on every request, and vet each package an assistant suggests.

  1. Keep Secrets Out of Code and Prompts12 min
  2. Treat Every Input as Hostile15 min
  3. Check Who Can See What15 min
  4. Vet Every Dependency15 min