Dream School AI Teacher Guide
Teacher Facilitation Guide • Grades 6–12 (Ages 11–18) Nov 15, 2026 · @Holly Clark
Building My Dream School With AI
Duration: 60 Minutes imagi × Lovable Integration
Core Concept
AI Building Literacy. Students find a real problem at their school, build an app to solve it with AI, and pitch it to the school leader.
Materials
Teaching slides (21 slides), prompt guide (placeholder link), Setup Guide, and the bilingual school map example.
Instructional Sequence & Pacing
| Step |
Time |
Focus |
Slides |
| Step 1 |
7 min |
What Is Vibe Coding? |
1–5 |
| Step 2 |
8 min |
The Challenge & the Plan |
6–9 |
| Step 3 |
8 min |
Teacher Demo: Bilingual School Map |
10–12 |
| Step 4 |
20 min |
Student Build & Iterate |
13–16 |
| Step 5 |
9 min |
Test & Improve |
17–18 |
| Step 6 |
8 min |
Pitch & Exit Ticket |
19–20 |
| Extension |
Optional |
How will you pitch your idea? |
21 |
Before Class Checklist (15–20 Mins Prep)
- imagi Classroom: Log in at edu.imagilabs.com and verify your classroom. Follow the setup instructions if this is a new class.
- Add Students: Populate the roster and print student logins (username, class access code, password).
- Activate Lovable: Toggle ON the Lovable AI tool in classroom settings.
- Credit Allocation: Assign ~50 credits per student (1 build = 10–20 credits).
- Slides: Open the teaching slides. Setup notes and the video link are in the speaker notes on slide 1.
- Prompt Guide: Open the online prompt guide (keeps the lesson within an hour). Print the Student Planning template only if you want paper copies.
- Backup Build: Run the demo prompt once before class in case the live demo fails.
Step 1 What Is Vibe Coding? (5 Minutes)
Slides 1–5
Key Definition: Vibe coding is creating software where humans direct the logic and vision in clear everyday language while AI writes the code. A prompt is the instructions you type to tell the AI what to build.
Crucial Teaching Point — AI Fills the Gaps: AI makes mistakes, including security flaws, and it will fill in anything you don't directly prompt it to do. Prompts must be detailed enough to get what you want.
Play the Intro to AI and Vibe Coding video (4 min) on slide 1, then move through slides 2–5. On slide 3, ask: "What would the AI have to guess with 'Make a school map'?"
Step 2 The Challenge & the Plan (8 Minutes)
Slides 6–9
The Challenge: "Our school leader wants to improve our school. What is one thing you could improve today to help us build a dream school?"
- Problem first (slides 6–8): In pairs or groups, students pick ONE small, real problem at school. Use the topic list on slide 8 or the Ideas Page in the Teacher Guide. Teacher example: new students get lost, especially when they don't speak the language.
- Then the solution (slide 9): Groups decide how an app could solve it: a game, an interactive map, a website, or something else. Lovable builds interactive apps, not printed documents. Show the example builds if they need inspiration.
- Pause before building: "But first, let's watch one app build together."
Step 3 Teacher Demo: Bilingual School Map (8 Minutes)
Slides 10–12
Open edu.imagilabs.com on the projector, launch Lovable, and paste the exact prompt below. Read each sentence aloud and ask students what part of the app it controls:
"Build me an interactive map for my school. It would be for bilingual students and teachers. On the first page, the user can select a language from a button at the top, then click on a room, and it says the name in that language."
While it builds, read the AI's "thought questions" aloud.
The Review (slide 11)
Ask: Does it work? What should we change? How did the AI decide what to build? Land the point: AI predicts code from patterns. It doesn't know our school, so it guesses and adds things you didn't ask for.
Close the Gap (slide 12)
Open the finished example. Ask: "What changes do we need to ask for in the prompt?" Draft one improvement prompt together using real school details, but never real names or photos.
Student Practice, Iteration & Assessment
Step 4 Student Build & Iterate (20 Minutes)
Slides 13–16
- Scaffolded Planning First (slides 13–14): Before opening Lovable, students use the online prompt guide to think through how their app will solve their problem. They read the prompt it generates and check that it describes what they want to build.
- Login & Generation (slide 15): Students log into edu.imagilabs.com, go to Projects, create a Lovable project, and paste their prompt. Remind them building takes a few minutes, and to picture what success will look like while it builds.
- Fix It (slide 16): Students test their first build and write down 3 things they expected but didn't get, then put all 3 in ONE prompt.
The "Expected vs. Reality" Debug Technique
"I expected [what should happen, e.g., the room name to switch to Spanish], but actually [what happened, e.g., it stayed in English]. Please fix this. Keep everything else the same."
Credit Management Rule: Enforce the 4-Prompt Strategy
Prompt 1 Build
Prompt 2 Fix
Prompt 3 Include more people
Prompt 4 Spare
Step 5 Test & Improve (9 Minutes)
Slides 17–18
Test (4 min): In pairs, partners test each other's apps and ask:
- Who would use this app, and how would it make our school better?
- What did the AI assume about our school?
- Is AI the right tool for this problem?
Improve (5 min): Students use the feedback to write their next prompt. Every student makes at least ONE change that makes the app more inclusive, like clearer words, a language option, or bigger buttons.
Step 6 Pitch & Exit Ticket (8 Minutes)
Slides 19–20
In groups, students give a 30-second pitch of their app, with one student playing the school leader. They cover the problem, the app (show it), and why it matters.
Have students answer one exit ticket question:
- What did the AI get wrong about our school, and how did you fix it?
- What change did you make so more people could use your app?
- Who should see your app next to make a real change?
Extension (Slide 21): Students choose how to present their idea to the real school leader, student council, or anyone who could use it to make a change.
Troubleshooting & Common Pitfalls
| Student says |
What to do |
| "The app didn't change!" |
The prompt was too vague. Tell students to name the exact part (e.g. "the language button" or "the room labels"). |
| "It broke what was working!" |
Prompt AI: "Keep everything else the same. Only change [specific part]." |
| "I don't have an idea." |
Point to the topic list on slide 8 or the example builds on slide 9. Start from the demo prompt and change one thing. |
If you like this, try our Build Your First Game with AI lesson!