Vibe mindset
What is Vibe Coding?
Understand the loop that turns plain-language intent into shipped software with AI as your pair builder.
Hook
You have an idea for an app, but tutorials still assume you will type every line by hand. Vibe coding is different: you direct AI with clear intent, then review what it builds like a tech lead.
Concept
Vibe coding is building software by describing outcomes, constraints, and quality bars — then iterating with AI tools until something real ships.
The loop:
- Think — What should exist? For whom?
- Prompt — Role, context, constraints, output format
- Review — Diff, tests, security, UX
- Ship — Deploy, measure, share
Try it
- Open Cursor or your preferred IDE.
- Paste the prompt below into Composer (Agent mode).
- Read the output — do not accept blindly. List two things you would change.
Prompt box
You are a patient teacher. In 200 words, explain vibe coding to a designer who has never shipped code.
Include one analogy and one anti-pattern (what vibe coding is NOT).
Checkpoint
- I can name all four steps of the loop
- I reviewed AI output critically, not copy-pasted
- I know where challenges and tools live on vibecodii
Ship artifact
Write three sentences in your own words: what you will build first with vibe coding. Save in a note — you will use it in the next lesson.
Codii tip
If the AI sounds too confident, ask: "What could break in production?" — that one question separates vibes from engineering.
Per-lesson notes sync across devices in v1.5. For now, use an external doc or mark lessons complete to track progress.
What's next
Continue with “Think → prompt → ship” or browse the full track.