Each episode closes a ticket from a real CTE program in about fifteen minutes. Those builds are listed episode by episode on the podcast page.
Vibe-coded apps from Vibe Labs and the community
Vibe Lab Exchange
See it built. Try it. Remix it. Share yours.
Every tool here started as a real problem from a CTE program and was vibe coded into something that works, in a Vibe Lab workshop or by an educator who took the method home. Each card shows the AI used, the standards it aligns to and a starter prompt, so you can try it with your students, build your own, and send it in. Builds from the CTE Vibe Lab podcast are on the podcast page.
- 13Vibe Lab builds
- 3AI tools used
- 0From the community
Where builds come from
Where the builds come from.
Apps built in Vibe Lab workshops and sessions, starting with the examples from the Vibe Lab page. With teachers' permission, the best workshop builds are added here.
Educators who listen to the show or took part in a Vibe Lab send in what they built back home. Reviewed builds are posted with credit.
The builds
Find a build for your program.
Share your build
Built something with AI for your program? Put it in the Exchange.
Listeners, Vibe Lab participants and any CTE or academic educator can submit a build. Apps, animations, simulations, workflows and media all count, from a quick calculator to a full pathway toolkit, built with any AI tool.
What to send
- The build. A link anyone can open: a shared app, a published page, a doc or a video walkthrough.
- The problem. What it solves, which pathway it's for and who uses it.
- How you built it. The AI tool, and your key prompts if you're willing to share them.
- Where you built it. At home, after a podcast episode, or at a Vibe Lab (name the event).
- The standard. The CTE standard or competency it maps to, if you know it.
- How to credit you. Your name, school or program, the way you want it shown.
The form opens in Google Forms. Please leave out student names and any private student information. Have a problem, not a build yet? Submit a ticket for the podcast.
Before you submit
- It's your own work, or your team's, and you have the right to share it.
- No student names, photos or private student information in the build or the submission.
- Any student data in the build is made up or removed.
- You keep ownership. Submitting gives CTELab.ai permission to list, link and describe your build here and on the podcast.
- Every build is reviewed before it's posted, and not every build is posted.
-
01
Submit
Send the link, the problem it solves and how you built it.
-
02
Review
Michael tries the build and checks it for accuracy, privacy and safety. You'll hear back by email.
-
03
Posted
Accepted builds go into the Exchange with credit to you. Standout builds may get a shout-out on the podcast.
Common questions
Using and sharing builds.
Can I use these builds with my students?
Yes, that's the point. Try a build first, check it against your own trade knowledge and your school's AI and privacy policies, and adapt it for your program.
What does "remix" mean?
Start from someone else's build and its prompts instead of a blank page, then change it for your pathway, your shop or your students. When a build shares its prompts, the "Prompts & remix" link shows you where to start.
Do I need to be a coder to submit?
No. Most builds here were made by describing what was needed in plain language and refining it with AI. If you're new to the method, start with the podcast or a Vibe Lab workshop.
Can students submit builds?
Student work is welcome when a teacher submits it, with credit to the program rather than to individual students.
Where are the podcast builds?
On the podcast page. The Season 1 builds are listed there episode by episode, and each one gets its link and prompts after its episode is released.
Build more