Lesson 15 of 65 · Free to read
Day 15 ΓÇö Mini-project
Month 1 · Week 3 — Visual AI builders & shipping MVPs fast Audience: Final-year students & early-career engineers (0–3 years) Format: Self-paced study + optional live clinic · Suggested time: 4–6 focused hours Key tools: Lovable / Replit / Bolt.new
Overview
Ship one visual-builder MVP and write an engineer’s retro: where the AI struggled, what you’d rewrite in code, and how you steered. Meta-learning is the point of Week 3 — this is the judgment employers hire for.
Learning objectives
By the end of this session, you can:
- Explain the core ideas behind: Mini-project: ship a visual-builder MVP and write an engineer’s retro.
- Apply the ideas using Lovable / Replit / Bolt.new on a realistic task (capstone, internship, or first-job style)
- Produce the exercise deliverable with clear success criteria
- Identify common failure modes and how to recover
- Capture at least one reusable prompt, rule, or checklist for your personal library
- Decide what must remain human-reviewed for this class of work
Core concepts
Choose one platform and finish
Switching tools mid-build destroys learning. Constraints create craft.
Retro structure
What worked, what hallucinated, how you steered, what you’d rebuild in a real repo for a job or capstone.
Tooling for today
Primary tools: Lovable / Replit / Bolt.new. Prefer official docs when APIs change. When a model invents a symbol, verify against source or docs immediately.
Practice posture
You are a final-year or early-career engineer pairing with a very fast teammate (the model): clear intent, grounded context, inspect consequential changes, keep a paper trail (commits, prompts, decisions).
Process diagram
Watch & learn
Study these free videos before or during the exercise. Each embed is chosen to reinforce today's objectives.
Course video
Course video
Worked example / case study
Scenario
Deliver shareable app + one-page engineer retro.
Step-by-step
- Clarify the outcome in one sentence tied to the exercise below.
- Gather grounding context (files, docs, schema, acceptance checks).
- Run the primary tool(s): Lovable / Replit / Bolt.new.
- Produce the smallest vertical slice that proves the idea.
- Verify with a command, test, screenshot, or side-by-side comparison.
- Write down one steering note — what you told the AI when it went wrong.
Sample prompt you can adapt
Role: Senior engineer mentoring an early-career developer (pairing with me).
Task: Mini-project: ship a visual-builder MVP and write an engineer’s retro.
Context: Final-year / early-career project (capstone, internship, or junior role).
Constraints:
- Match existing project patterns
- No new dependencies unless justified
- Include tests or a verification checklist
- Call out assumptions explicitly
Output: step plan first, then code/files, then verification commands.
Hands-on exercise
Primary task. Pick one platform and deliver a working, shareable app, plus a short retro on where the AI struggled, what you’d rewrite in code, and how you steered it.
Coaching notes
Include a 60-second demo script you could use in an interview.
Steps
- Set up or open the workspace required by: Lovable / Replit / Bolt.new.
- Skim today's core concepts and watch the video(s) before prompting.
- Execute the task in small commits (or saved artifacts if no-code).
- Fill the success checklist below.
- Note one surprise and one process improvement for tomorrow.
Success criteria
- Deliverable matches the exercise description
- You can explain every AI-generated change in plain language
- Verification ran (tests, manual check, or published URL)
- At least one pitfall from this lesson was consciously avoided
- Artifact saved (repo commit, doc, or published link)
Timebox
Suggested: 90–150 minutes of focused build time after study.
Templates & checklists
| Asset | Purpose |
|---|---|
| Prompt stub | Reuse today's structure (role → task → constraints → format) |
| Verification checklist | Tests / manual QA / security skim |
| Decision log | What you delegated vs kept human |
Copy-paste prompt skeleton
## Goal
Mini-project: ship a visual-builder MVP and write an engineer’s retro.
## Context files
- (list paths)
## Constraints
- Stack: (fill)
- Do not: (secrets, drive-by refactors)
## Definition of done
- Pick one platform and deliver a working, shareable app, plus a short retro on where the AI struggled, what you’d rewrite in code, and how you steered it.
Daily reflection (3 minutes)
- What did AI do well?
- Where did it confidently fail?
- What rule will you add to your cookbook/rules file?
Common pitfalls
- Restarting from scratch instead of steering
- Retro that only praises the tool
- No public link
Key takeaways
- Finished > perfect
- Retros build transferable skill
- Steering stories impress hiring managers
- Tools (Lovable / Replit / Bolt.new) change; the judgment skills transfer.
Resources
- Official docs for: Lovable / Replit / Bolt.new
- Course cookbook: keep prompts in a versioned Markdown file in your repo
- Prior days this week — skim objectives if you skipped ahead
Self-paced lesson — Mastering AI-Assisted Development & Vibe Coding — Day 15 of 65.