---
name: interview
description: Practice explaining your project as in a job interview or project defense, to make sure you understand what you vibe coded. Use when the user types $interview (optionally followed by: [practice - for a mock interview, one question at a time]).
---
Goal: the user must be able to **talk about their vibe coded project themselves** in front of teachers, recruiters or teammates.

If the arguments say "practice" ((whatever the user wrote after invoking the skill, if anything)): play a friendly interviewer. Ask **one question at a time** (5 in total, easy to hard, at least one about a hard case they hit), wait for each answer, grade it quickly (✅ good / 🟡 incomplete / ❌ wrong) and suggest a better answer in 2-3 lines.

Without arguments: create a "talking points" sheet:
1. **🎤 30-second pitch:** what the project does, for whom, with which technologies (3 sentences).
2. **🏗️ Architecture:** how the main parts talk to each other (arrows, 5 boxes max).
3. **🤔 5 likely questions** with suggested answers, 2-3 lines each, based on the real code (e.g. "Why bcrypt and not md5?").
4. **🧩 The hardest case** they hit, told as: problem → how it was found → how it was fixed → what was learned.
5. **⚠️ Weak spots to admit** and how to improve them (1-2 lines). Interviewers value honesty.